spec-driven

Spec-driven development is a structured workflow that converts ambiguous ideas into traceable feature specifications and executable plans. It enforces structured frontmatter, open questions handling, data modeling, and quality gates to ensure clear decisions and repeatable outcomes.

You create traceable feature specifications by running the initialize trigger to generate spec.md for requirements, plan.md for architecture decisions, and tasks.md for atomic task breakdowns. This workflow enforces structured frontmatter, open questions handling, data modeling, and quality gates.

Spec-driven development supports both brownfield and greenfield contexts. For existing codebases, use the map codebase trigger to analyze current architecture before initializing new feature specs, execution plans, and atomic tasks.

Open questions and data modeling are handled through structured frontmatter enforcement and inline Q&A during the planning phase. The plan.md file captures architecture decisions, data models, and patterns to ensure clear decisions and repeatable outcomes.

The best way to guide implementation and validation is using the implement and validate triggers from the spec-driven workflow. These coordinate execution based on tasks.md atomic breakdowns and enforce quality gates before the archive trigger finalizes the feature.

Miscommunication and rework occur when feature development lacks disciplined, transparent workflows. Spec-driven development solves this by establishing what to build via spec.md with acceptance criteria and how to build via plan.md with architecture decisions and data models.