kiro-skill

This Skill automates the creation of feature specifications in EARS format, design documents, and implementation task lists. It transforms ideas into organized, phase-gated outputs stored in `.kiro/specs/{feature-name}/`, enforcing explicit approvals between each phase of development.

EARS (Easy Approach to Requirements Syntax) is a structured format for writing clear, testable acceptance criteria. This Skill applies EARS when documenting new feature requirements, ensuring requirements are unambiguous and directly tied to implementation tasks.

This Skill stores specifications and task lists under `.kiro/specs/{feature-name}/` using kebab-case naming conventions. It generates requirements.md, design documents, and incremental test-driven task lists in a single, centralized location for each feature.

Yes. This Skill is designed for features requiring phased planning, generating both design documents and step-by-step implementation task lists that follow test-driven development practices from the start.

This Skill enforces phase-gated outputs, requiring explicit approval before proceeding from requirements to design to implementation. Skipping gates is not permitted; each phase must be reviewed and approved to move forward.

This Skill is optimized for features and ideas requiring documented requirements, architecture design, and structured implementation plans. It is most effective for substantive changes where specification and planning reduce ambiguity and rework.