What problem does it solve? Writing clear, testable requirements is slow and error-prone, and vague acceptance criteria cause rework later in design and implementation. This Skill generates a complete requirements document that follows EARS syntax, respects project steering context, and passes a built-in review gate before anything is written to disk. ## Core Features & Use Cases - EARS-Compliant Requirements Generation: Produces acceptance criteria in event-driven, state-driven, unwanted-behavior, optional-feature, and ubiquitous patterns, in English or Japanese based on spec.json language settings. - Built-in Review Gate: Runs mechanical and judgment-based checks (numeric IDs, EARS triggers, no implementation details) with up to two repair passes before writing requirements.md. - Context-Aware Scope Boundaries: Reads steering files, briefs, and templates to make inclusion/exclusion boundaries explicit while keeping technology choices out of requirements. - Use Case: After drafting a feature brief for a checkout service, run the Skill to produce a reviewed requirements.md with numbered requirements and EARS acceptance criteria, then proceed directly to the design phase. ## Quick Start Ask the agent to generate requirements for your spec by running the kiro-spec-requirements skill with your spec name, for example: generate requirements for the checkout-feature spec.
