kiro-spec-requirements

Generating EARS-format requirements involves reading project descriptions and steering files to draft grouped, testable acceptance criteria. The skill automates this by applying EARS patterns to feature-level specs and producing drafts for review.

EARS syntax is a structured phrasing method for writing unambiguous, testable requirements. It reduces implementation-level statements by using specific conditional clauses, ensuring acceptance criteria remain clear and verifiable.

Structuring feature-level specs in .kiro/specs requires organizing project descriptions and steering context into coherent requirement areas. The skill reads these files to apply language settings and boundary candidates for drafting requirements.

A requirements review gate works by running mechanical and judgment-based checks on drafted requirements. It repairs local issues, enforces EARS compliance, and updates requirements.md and spec.json metadata only when the gate passes.

Yes, you can group acceptance criteria by functionality areas. The skill drafts requirements by grouping functionality into coherent areas based on collected language, scope, and boundary candidates from steering documents.

Product spec requirements often contain ambiguous statements when they lack structured EARS patterns and include implementation-level details. Applying guideline-driven drafting from steering context ensures requirements remain testable and unambiguous.