Creates a technical plan from a functional spec. Defines HOW to build it: architecture decisions, data models, testing strategy, constraints. Reads the actual codebase for context. Use when user says "plan this", "technical plan", "how to build", "architect", "design the solution", or after running /spec. Do NOT use without a spec — run /spec first.
Commits, pushes, and opens a pull request for completed work. Uses Conventional Commits format and gh CLI for PR creation. Use when user says "ship", "create PR", "open pull request", "push", "ship it", "commit and PR", or after running /implement. Do NOT use without running /review first or with failing tests. All tests must be passing before shipping.
Writes a functional specification for a feature, bug fix, or change. Describes WHAT to build, not HOW. Uses Given/When/Then acceptance criteria. Technology-agnostic. Use when user says "write spec", "specify feature", "define requirements", "what should this do", or pastes a user story / PRD / feature request. Do NOT include implementation details — use /plan for that.
Closes the SDD loop after a PR merges by consolidating review findings, post-review commits, and user-stated lessons into the repo-scoped wiki. Locates the preliminary wiki page by PR number, gathers post-merge context via gh CLI, then delegates to /sdd:wiki-ingest --final with cross-references back to the preliminary. Use when user says "close loop", "wiki close-loop", "post-merge ingest", "archive lessons", or after merging a PR that has a preliminary wiki entry. Do NOT use before the PR is merged — the lessons are not yet final. Do NOT use for spec/plan/tasks ingestion (that is /ship Step 9).
Ingests SDD artifacts (spec, plan, tasks summary, review findings, lessons) into the repo-scoped `.wiki/` knowledge base. Two modes: `--preliminary` (post-ship, pre-merge) writes spec/plan/tasks-summary pages; `--final` (post-merge) writes review-findings and lessons pages cross-linked to the preliminary. Use when user says "ingest wiki", "save to wiki", "archive to wiki", "write to .wiki", or when /ship/close-loop delegate here. Do NOT use for wiki consultation (that is handled inline by /spec, /plan, and /wiki:close-loop via scripts/wiki-query.sh). Do NOT write wiki pages without explicit user confirmation.
Automates batch file migrations from one pattern to another. Language and framework agnostic. Use when user says "migrate files", "batch migration", "convert all files from X to Y", "replace pattern across files", "mass refactor", or "migrate codebase". Do NOT use for single-file changes or non-migration refactors.
Validates completed batch migrations for consistency and correctness. Checks for residual old patterns, runs tests, verifies build, and generates a quality report. Use when user says "review migration", "validate migration", "check migration status", "verify batch changes", or after running /migrate. Do NOT use if no migration has been performed.
Orchestrates the complete Spec Driven Development pipeline: spec -> plan -> tasks -> implement -> review -> ship. Use when user says "new feature", "full development cycle", "run", "build this end to end", "start feature", or provides a user story / PRD to implement from scratch. Do NOT use for quick fixes or single-file changes — use individual phase skills instead.