sdd-specification

Feature specifications follow the Specification-Driven Development framework with standardized sections: Title, Overview, User Stories, Functional Requirements, Acceptance Criteria, Technical Considerations, Dependencies, Risks, and Success Metrics. Run /specify to generate a complete spec.md template that enforces these sections and ensures comprehensive documentation before planning.

Specification-Driven Development (SDD) is a methodology that standardizes feature documentation upfront by requiring structured, testable requirements across multiple dimensions. Use it when starting new features, documenting requirements, or ensuring teams have aligned, detailed specifications before development begins.

Domain detection automatically identifies relevant domains and suggests agents to include in your feature specification during the /specify command execution. This output prepares artifacts for the planning phase by clarifying scope and team responsibilities across detected technical domains.

Yes. The specification automation includes built-in validation against the spec-template.md structure and constitutional criteria. After generating your spec.md, validation readiness checks ensure all required sections are completed before moving to the planning phase.

Acceptance Criteria define testable conditions that confirm a feature works as intended, while Functional Requirements detail what the feature must do. Both sections enforce structured documentation so teams understand expected behavior and can write tests directly from the specification.

The tool generates the specification file automatically. Run /specify to produce a complete spec.md with all required sections pre-populated according to the SDD template, then refine content and validate against the framework before proceeding to planning.