spec-firstlisted

# Spec-First Development ## Contract Inputs: - User request describing a feature, project, or non-trivial implementation task. Outputs: - Stage A framing with 3 approaches and tradeoffs. - Draft `spec-[feature-name].md` content for `.agents/memory/`. - Draft `todo.md` checklist with per-step verification commands. Creates/Modifies: - `.agents/memory/spec-[feature-name].md` (spec artifact). - `.agents/memory/decisions-[feature-name].md` (decision log). - GitHub Issue (checklist body for active todo tracking). External Side Effects: - Creates GitHub Issues via the gh CLI when creating todo tracking. Confirmation Required: - Before creating GitHub Issues. - Before proceeding from Stage C to Stage D (execution). Delegates To: - `prd-task-creator` for PRD-style issue creation. - `executing-plans` for Stage D autonomous execution. A structured workflow for LLM-assisted coding that delays implementation until decisions are explicit. ## When This Activates - "Build X" or "Create Y" (new features/projects) - "Implement..." (non-trivial functionality) - "Add a feature that..." (multi-step work) - Any request requiring 3+ files or unclear requirements ## When to Skip - Single-file changes under 50 lines - Typo fixes, log additions, config tweaks - User explicitly says "just do it" or "quick fix" ## Core Principles 1. **Delay implementation until tradeoffs are explicit** — Use conversation to clarify constraints, compare options, surface risks. Only then write code.