architectlisted

# Staged Build Methodology Drive software projects through a structured lifecycle that prevents the #1 AI coding failure: losing context on a big plan and missing pieces. ## When NOT to use this skill - Task is a quick script, one-off fix, or single-file change → just build it directly - User wants to edit existing code, not plan a new project → edit directly - Scope is entirely clear and fits in one session without a plan → skip the methodology - User explicitly says "just do it" without wanting a plan → respect that --- ## Quick Reference | Phase | What happens | Gate to pass | |-------|-------------|--------------| | 0 | Technical spike — validate riskiest constraint | PROJECT_STATE.md with validated constraint | | 1 | Design notes — one per domain, no code | All domains covered, user confirms | | 1.5 | Build order — dependency graph, stage sequence | _build-order.md reviewed + approved | | 2+Execute | Write 2-3 stages → build → repeat | All tests green, stage committed | Full methodology: `references/methodology.md` · Testing obligations: `references/testing.md` · Stage format: `references/stage-template.md` --- **Core rule:** Never work from one giant plan. Atomize into stages small enough to hold entirely in context, execute correctly, and validate before moving on. ## Invocation | Input | Action | |-------|--------| | Bare (`/architect`) | Ask: "New project or resuming an existing one?" | | With project description | Assess scope (see Scaling Tiers), then st