Spec-Driven Development

Creates structured specifications before writing code to clarify requirements, surface assumptions, and define success criteria, reducing rework and miscommunication.

Generate a step-by-step construction plan from a one-line objective, with dependency graphs, parallel step detection, and adversarial review for multi-session engineering projects.

Turn a design or spec document into a working MVP by planning thin vertical slices, scaffolding the first slice, then building iteratively with test-driven development and gated commits.

Generate a structured specification document before writing implementation code, validating scope, drafting specs, and registering them in the project.

Implements tasks from an OpenSpec change, guiding the agent through selecting a change, reading context, and completing tasks with progress tracking.

Translate a vague request or GitHub issue into a concrete, testable spec using five structured elements (problem, scope, acceptance criteria, edge cases, success criterion) before writing any code. Prevents scope creep, PR churn, and mid-implementation pivots.

Implements code features phase by phase from a JSON or Markdown plan, with configurable unit-test and quality-gate choices, token-budgeted execution, and resumable state.

Guides users through the specification-driven development workflow, from requirements gathering through specification, test derivation, implementation, and validation.

Implements tasks from an OpenSpec change, tracking progress and pausing for clarification when needed.