sdd-requirements

To generate EARS-formatted requirements for a new feature, provide the feature name and context to produce a structured requirements document complete with testable functional and non-functional requirements.

EARS syntax is a structured approach for writing software requirements specifications, utilizing Ubiquitous, Event-Driven, and State-Driven formats to ensure clear, testable acceptance criteria and feature documentation.

You can create testable acceptance criteria from feature specifications by applying the EARS process, which aligns user stories and steering documents into traceable functional and non-functional requirements.

Yes, requirements generation integrates with SDD workflow status tracking by utilizing MCP tools like sdd-init, sdd-status, and sdd-approve to streamline feature initialization and readiness checks.

Generating requirements documents uses project steering references to ensure alignment, producing structured output directly at .spec/specs/{feature}/requirements.md with clear traceability to your feature specs.

Use EARS requirements over standard user stories when you need standardized, unambiguous documentation with strict traceability, ensuring that both functional and non-functional requirements have clear, testable acceptance criteria.