kiro-spec-requirements

To generate EARS-format acceptance criteria, provide a project description and steering context. The system produces testable, user-observable requirements using event, state, and unwanted-behavior patterns while maintaining consistent subject naming.

The EARS format structures testable software requirements using specific patterns for events, states, and unwanted behaviors. It reduces ambiguity by converting project descriptions into explicit, testable user-observable acceptance criteria with clear inclusion and exclusion boundaries.

You can enforce a review gate on requirements specifications by running mechanical and judgment checks. The system evaluates drafts, repairs them up to two times, prompts you on real ambiguities, and writes the requirements.md file only after the gate passes.

Yes, you can use steering files like product.md, tech.md, and structure.md to preserve terminology and scope decisions. The system reads these local templates and .kiro/specs directories to ensure context-aware drafting of your requirements.

No, generating EARS requirements does not introduce implementation details into the specification. The system produces testable acceptance criteria and explicit inclusion or exclusion boundaries while strictly keeping implementation specifics out of the finalized requirements.md.

The best way to define explicit inclusion and exclusion boundaries is converting steering context into EARS-pattern acceptance criteria. This method applies judgment review gates to repair ambiguities and establishes clear, testable scope limits for feature workflows.