Archives completed roadmap phases from specs/roadmap.md into specs/changelog.md, compressed to title, completion date, and a one-sentence outcome with a link back to the spec directory. Use when phases are finished and the roadmap should track only open/upcoming work, or when asked to "update the changelog" / "move completed phases out of the roadmap."
Creates a "constitution" for an existing (brownfield) project — a mission statement, tech-stack overview, and phased roadmap — written as markdown files in a specs/ directory. Use when starting work on an existing codebase to clarify goals and plan implementation. Trigger when the user says "create the constitution", "brownfield constitution", "set up specs for this repo", or invokes /sdd-constitution-brownfield.
Creates a "constitution" for a new (greenfield) project — a mission statement, tech-stack overview with database schema, and phased roadmap — written as markdown files in a specs/ directory. Use as the first step of spec-driven development when starting a project from scratch, before any feature work. Trigger when the user says "create the constitution", "greenfield constitution", "start a new project", "set up specs", or invokes /sdd-constitution-greenfield.
Kicks off a new feature by finding the next incomplete phase in specs/roadmap.md, creating a git branch, interviewing the user about scope/decisions/context, and writing a dated spec directory under specs/ containing plan.md, requirements.md, and validation.md. Trigger when the user says "feature spec", "next phase", "start the next feature", or invokes /sdd-feature-spec.
Implements the current feature branch against its spec — working through plan.md task group by task group, validating against validation.md, and marking the phase complete in specs/roadmap.md. Use after a feature spec exists (plan.md, requirements.md, validation.md in a dated specs/ directory) and you're ready to write code. Trigger when the user says "implement the plan", "implement the feature", "build this phase", or invokes /sdd-implement-feature.
Independently validates a completed feature branch against its validation.md acceptance criteria and produces FEATURE_DIR/validation-report.md. Reads code, tests, and criteria; runs tests; never edits production code or specs; stays deliberately blind to plan.md. Run in a SEPARATE agent session from the one that implemented the feature. Trigger when the user says "validate the feature", "independent validation", "validation report", or invokes /sdd-validate-feature.
Pre-flight checklist run between SDD cycles — before picking up the next roadmap item or wrapping up for now. Verifies git state (uncommitted work, unmerged feature branch), surfaces the next roadmap candidate for the user to confirm, and prompts a context clear. Trigger when the user says "preflight", "pre-flight", "am I clear to start the next phase", "post planning", or invokes /sdd-preflight.
Reconciles the constitution (specs/mission.md, specs/tech-stack.md, specs/roadmap.md) with what was learned after a feature shipped — on a dedicated replanning branch. Updates mission/tech-stack if reality has drifted, re-scopes the roadmap, and surfaces the downstream impact on existing specs and code for the user to approve. Use after a feature is complete and merged, before starting the next one. Trigger when the user says "replan", "replanning", "update the constitution", or invokes /sdd-replan.