speckit-specify

A specification document should include problem framing, actors, goals, requirements, acceptance criteria, assumptions, constraints, success metrics, and user scenarios to ensure high-quality, testable content for product planning and handoffs.

To write testable acceptance criteria from informal feature descriptions, the Skill enforces a template-driven approach that extracts requirements and user scenarios, ensuring mandatory sections are filled for planning and reviews.

Generating product planning specs without a predefined template is not recommended; this Skill enforces a consistent template to guide drafting, ensuring mandatory sections like assumptions and constraints are addressed for collaboration-ready outputs.

The best way to automate feature extraction for product requirements is providing a plain language feature description to this Skill, which transforms it into a structured spec suitable for traceable decisions and optional clarifications during hand-offs.

Generating specification documents with this approach requires no specific frameworks or external dependencies; it operates independently to translate plain text feature ideas into precise, actionable specs.