Recon Issue
Deep implementation plan for one issue before coding.
What it is
Section titled “What it is”Deep implementation plan for one issue before coding. 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”Planning a single change set reduces thrash and oversized PRs. Small batches and clear acceptance criteria (BDD-style) make the subsequent fix-it / test-it / pulls path reviewable.
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”03-smallest-next-step, 04-evidence-over-vibes
Further reading
Section titled “Further reading”See also the handbook Sources & grounding bibliography.
Agent skill
Section titled “Agent skill”recon issue