kiro-skill

EARS (Easy Approach to Requirements Syntax) provides a standardized way to write testable acceptance criteria. Kiro automates this by generating requirements.md in EARS format during the requirements phase, ensuring clear, verifiable conditions for each feature.

Yes. Kiro converts feature ideas into a phased workflow that produces structured requirements, design documents, and task breakdowns stored in .kiro/specs/{feature-name}/, eliminating manual planning steps.

Spec-driven development separates concerns into phases: requirements definition, design, task planning, then execution. Kiro guides you through each phase sequentially, storing outputs in dedicated feature directories with kebab-case naming.

Kiro links requirements, design, and tasks into a single workflow where design decisions reference requirements and tasks reference both. This traceability keeps documentation synchronized throughout feature development.

No. Kiro structures the feature development process and provides templates for requirements and design phases. You supply the feature idea and domain knowledge; the workflow handles organization and documentation generation.