kiro-spec-requirements

EARS-format requirements are generated by converting project descriptions and steering context into structured text using specific patterns. This skill automates that conversion, ensuring every acceptance criterion follows EARS syntax before finalizing the document.

EARS syntax is a structured pattern for writing testable acceptance criteria. This skill automatically applies EARS patterns to your feature specifications, ensuring requirements are consistently formatted and review-ready without manual syntax work.

Automate requirements validation by running mechanical and judgment-based review gate checks. The skill performs up to two repair passes to fix issues automatically, then stops to ask clarifying questions if true ambiguities remain in the specification.

Yes, you can use steering files to draft feature specifications automatically. The skill reads available steering context and feature folders under .kiro/specs to produce initial requirements drafts that align with your existing project guidelines.

When requirements fail review gate checks, the skill executes a repair loop. It performs up to two automated repair passes to correct mechanical and judgment-based issues, only stopping to ask for human input on true ambiguities.

Update spec.json metadata by finalizing the generation status after the review gate passes. The skill automatically writes the requirements.md file and updates the phase and approval fields in spec.json to reflect the completed generation.