reconlisted

# /recon — Pre-Build Decision Intelligence ## What this skill produces A **decision brief** — one opinionated document (~200 lines max) that reads like a 30-minute briefing from a senior consultant who's built 10 of these. Not a research report. Not a comprehensive survey. A ranked list of what actually matters for *this* project at *this* scope, with traps and edges treated as equal halves of the work. The consultant's job has two sides: - **Downside:** what costs you if you get it wrong (traps, irreversible decisions, failure modes) - **Upside:** where the edge is that makes this an outlier (category-breaking moves, underused primitives, unfashionable advantages) Recon does both, balanced. Pure worry is useless. Pure optimism is useless. **Calibrated judgment is the product.** ## Modes | Mode | Trigger | Output | |------|---------|--------| | **Full** | `/recon` or `/recon [project description]` | Single decision brief + sources appendix | | **Focused** | `/recon [specific question]` | Mini decision brief on that question | Distinguish by intent: "building a task management app" = full. "auth patterns for multi-tenant SaaS" = focused. --- ## Phase 0: Orient and Calibrate Scope Determine what to research from the argument, conversation context, open files, and project state. **Scope calibration — mandatory.** Before any research, lock these down. This is what keeps recon from applying enterprise worries to prototypes (and enterprise aspirations to weekend hacks).