technical-recon
Technical recon of an already-groomed, stakeholder-accepted issue that the dev team has not yet vetted or sized — dispatch a read-only sub-agent (one per issue, in parallel for a batch) to trace the ask into the codebase, produce a verified implementation approach, assert a level-of-effort (LoE) estimate with confidence, surface risks/unknowns/dependencies, recommend a split when the work is too big for one PR, and pin the eventual dispatch model/effort/lane — then post the findings to the issue and move it to a dev-vetted state. Use whenever an engineering or project lead hands you one or more issue numbers/keys to 'recon', 'scope', 'size', 'estimate', 'tech-review', or 'assess implementation' before any code is written; also use when deciding whether a groomed issue is actually ready for a dev dispatch. This is the deeper dev-side pass, distinct from the cheap intake-triage recon in the issue-filing skill.
Pinned to revision 6b9d66f636cc, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.