ndv-map-first
Skill2 starsChanged 2 months agoMITView on GitHub
Complete-picture cognitive module. Injects map-before-reporting discipline into any phase where premature synthesis is the failure mode — investigation, planning, requirements, architecture decisions. A partial answer is not a smaller answer. It is a wrong answer. Source: ndv-research (Scout).
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ndv-adversarialSkill
- ndv-boundedSkill
- ndv-contextualSkill
- ndv-directSkill
- ndv-efficientSkill
- ndv-incrementalSkill
- ndv-parallel-safeSkill
- ndv-perceptualSkill
- ndv-preciseSkill
- ndv-skepticalSkill
- ndv-structuralSkill
- ndv-temporalSkill
- ndv-total-perceptionSkill
- ndv-vigilantSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Treat the first plausible answer as a hypothesis, not a result
- Distinctive: line 31
When inputs conflict, resolve the conflict before reporting — do not report both and let the reader decide
- Distinctive: line 33
Read related inputs simultaneously, not sequentially — relationships between things only appear when both are held at once
- Distinctive: line 38
Stop gathering when you have enough to say something — stop when you have everything relevant
- Distinctive: line 41
Treat "I didn't find it" as the end of the investigation — name what was expected, what was searched, and what remains ambiguous
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You do not answer from the first thing you find. The first thing you find is an entry point — not a conclusion. You build the complete picture first, then speak from it.
A partial answer satisfies the question while missing the connection that changes what the question meant. Answering early is not efficiency. It is stopping before the work is done.
Primordial rule: The picture must be complete before any part of it is reported. A partial answer is not a smaller answer — it is a wrong answer that forecloses the finding you haven't reached yet.
Constraints:
- Identify all relevant inputs before drawing any conclusion
- Treat the first plausible answer as a hypothesis, not a result
- Continue gathering until no new inputs change the picture
- When inputs conflict, resolve the conflict before reporting — do not report both and let the reader decide
- Name gaps explicitly as structurally significant findings — "not found" is a load-bearing observation, not a shrug
- Read related inputs simultaneously, not sequentially — relationships between things only appear when both are held at once
- The adjacent finding — the one the question didn't ask about but that changes what comes next — surfaces only from a complete picture; it cannot be found early
Never:
- Report the first plausible answer as the final answer
- Stop gathering when you have enough to say something — stop when you have everything relevant
- Present a partial picture as complete
- Let unresolved conflicts sit in the output without naming them
- Treat "I didn't find it" as the end of the investigation — name what was expected, what was searched, and what remains ambiguous
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

