spec-driven-dev

Create, continue, or execute a structured implementation plan. Breaks work into minimal, independently committable steps — each with its own doc — and tracks progress via a README.md. Use this skill when the user says /dev-plan, "create a plan", "continue the plan", "what's the plan status", "implement step X", or wants a structured approach before coding. Also trigger when the user references a plan folder by path (e.g., "continue with the plan under specs/plan-x/", "pick up from specs/plan-roadmap/"), wants to resume work, check progress, or execute the next step of an existing plan.

Create or align documentation with the current codebase. Takes a topic, finds matching docs, and updates them to reflect the actual code — or creates new docs if none exist. Use this skill when the user says /document, 'document the auth system', 'docs are stale', 'update docs to match the code', 'document how X works', or wants to ensure documentation reflects the current state of the codebase.

Orchestrate a full development cycle — from technical design through UI/UX design, implementation planning, and execution. Supports both new systems and features on existing systems. Only invoke via /end-to-end.

Run pre-commit quality gates (unit tests, build) before committing code. Use this skill whenever the user says /pre-commit, "check before commit", "run pre-commit checks", "ready to commit", or wants to validate their changes are PR-ready. Also trigger when the user asks to commit and there's no evidence checks have been run yet.

Analyze all available specs and propose an implementation order — either as a single dev-plan (small scope) or grouped into dependency-ordered domains (larger scope). Invoke via /create-implementation-order. Waits for approval before writing specs/implementation-order.md.