Feature development in phases. Light by default; weight only where the change pays for it.
Triggers
- Specify ("plan feature", "spec this", "from PRD", "modify feature", "discuss how to build") → specify.md
- Design ("design this feature", "technical design", "plan the build") → design.md
- Tasks ("create tasks", "break into tasks", "task breakdown") → tasks.md
- Implement ("implement task T-1", "implement T-1 to T-4", "implement slice S-1", "execute tasks", "implement everything") → implement.md
- Validate / UAT ("run UAT", "manual testing", "validate flows") → validate.md
- Archive ("archive feature", "archive this spec") → archive.md
Workflow
specify → design → tasks → implement → [validate] → [archive]
└────────┴────────┴──────────┴──────────┴ a mechanical change skips all of this: one-liner → branch → implement inline
Specify's triage decides the path: a mechanical change with zero load-bearing decisions becomes a one-liner straight to inline implement on its own branch, and a prompt carrying outcomes that ship separately becomes one feature per outcome. Everything else produces the artifacts and runs the phases in turn. Verify is mental, per task, inside implement — never a user phase. Validate is optional UAT on the running application. Archive is manual housekeeping for a feature in any state, never automatic or suggested.