sdd-spec-requirements

You can generate testable requirements by providing your project description and steering context to an automated specification tool, which outputs structured requirements in EARS format. This ensures all acceptance criteria follow a standardized, testable syntax.

EARS is an Event-driven, Actor, Response, State syntax used to write unambiguous, testable software requirements. It structures requirements to clearly define triggers, actors, expected responses, and system states for feature specifications.

To start spec-driven development, you define the initial feature specifications by generating a comprehensive requirements document from your project description. This creates the foundational, testable requirements needed for subsequent development phases.

Yes, steering context is required to generate EARS requirements. Loading project context from directories like docs/tasks/ and docs/steering/ ensures the generated requirements adhere to project constraints and specific EARS patterns.

Using the EARS format is the best way to structure acceptance criteria for automated testing. It transforms project descriptions into strict Event-driven, Actor, Response, and State syntax, making each requirement inherently testable.

Yes, you can use existing project specifications to create initial feature requirements. The specification process analyzes your project descriptions and applies EARS patterns to output a comprehensive, structured set of requirements for review.