Thinking Map Territory
When a claim, doc, test, metric, or assumption conflicts with observed behavior, stop...
Install
npx skills add tjboudreaux/cc-thinking-skills --skill thinking-map-territory -g -a claude-code -y- Repository
- tjboudreaux/cc-thinking-skills1.7k
- Category
- Testing
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Lightabout 768 tokens
- Runs scripts
- No, instructions only
What it does
When a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.
Map Territory
Docs, tests, diagrams, metrics, comments, and mental models are maps. Running code and actual data are the territory. When they disagree, verify territory and update the model, never force reality to match the description.
When to Use
- Observed behavior contradicts a doc, test expectation, diagram, comment, dashboard, or prior assumption.
- A claim about the system rests on a secondary source rather than current code or data.
- Tests pass but production or manual behavior is wrong.
- You are about to theorize why something happens before inspecting what happens.
- A decision depends on whether a model, schema, or metric is still current.
When NOT to Use
- The map is the artifact you are asked to edit (doc, diagram, spec), that artifact is the task territory.
- Same path already verified this session, reuse that observation.
- Map is authoritative and generative (codegen types, derived schema) with no claimed drift.
- The mismatch cannot change the decision, note and move on.
- Competing causal hypotheses after territory is confirmed, switch to scientific-method.
- Security exploit construction, use red-team; this skill only settles model-versus-observation.
