Vision / Why
Recover or write why the project exists before picking tools.
What it is
Section titled “What it is”Recover or write why the project exists before picking tools. This practice is a skill-mapped TTP: when, why, and which command—not a full copy of the skill. Open the skill to execute.
Why it works
Section titled “Why it works”Without a stated purpose, teams optimize motion. Outcome-oriented framing (jobs-to-be-done style) and Diátaxis’s purpose-first docs keep subsequent strategy/skill choices accountable.
When to use it
Section titled “When to use it”When the situation matches the one-liner above and Orientation (or your project path) says this is the fire to touch now.
- Invoke the skill; follow its safety rules
- Keep one write owner; collect evidence before claiming done
- Hand off to the next practice instead of boiling the ocean
- Skip orientation when you’re lost
- Spawn overlapping agents to “go faster”
- Treat the practice as done without evidence
Related concepts
Section titled “Related concepts”08-vision-tied-goals, 01-this-is-fine-stance
Further reading
Section titled “Further reading”See also the handbook Sources & grounding bibliography.
Agent skill
Section titled “Agent skill”idk-now vision · document-it · DocSlime