kiro-spec-requirements

EARS-format requirements are generated by synthesizing your project description with steering context files like brief.md and spec.json. The system produces testable, EARS-compliant acceptance criteria and enforces numeric requirement headings for clear, unambiguous scoping.

The EARS format is a structured method for writing testable, unambiguous software requirements. It uses specific language patterns to define acceptance criteria, ensuring that every requirement is clear, verifiable, and free of hidden assumptions during spec-driven development.

You run the requirements review gate to validate EARS compliance, check coverage, and enforce numeric headings before writing requirements.md. This gate ensures all acceptance criteria are unambiguous and aligned with steering context before phase approval.

Yes, steering files such as brief.md, requirements.md, and spec.json are synthesized to inform the scope, language, and constraints of your feature requirements. The system applies these inputs to generate context-aware, EARS-compliant acceptance criteria.

You update spec.json metadata by setting the current phase and approval flags after requirements are validated. The system writes the finalized requirements.md and advises on next-phase actions like design, gap validation, or rework based on these metadata updates.