kiro-specs_skill

Overview

This skill generates a complete Kiro-style spec pack for a feature and stores it under .kiro/specs/{feature-name}/. It produces requirements with EARS acceptance criteria, a design document with correctness properties, and an executable implementation tasks checklist. The workflow enforces sequential phases, explicit approval after each artifact, and single-task execution.

How this skill works

The skill inspects the repository for a .kiro/specs/ directory and existing feature folders to determine the current phase. It can create or update three phase files: requirements.md (EARS-formatted user stories and acceptance criteria), design.md (architecture, interfaces, and correctness properties), and tasks.md (a checked-off implementation plan). After generating each artifact it requests user approval before proceeding to the next phase.

When to use it

• When you need a formal spec/PRD/RFC for a new feature in .kiro/specs/
• When converting high-level requests into EARS acceptance criteria
• When you need an architecture/design doc that links to requirements
• When you want an executable task checklist for implementation
• When enforcing a sequential, review-driven development flow

Best practices

• Create requirements first and do not skip to design or tasks
• Write acceptance criteria in EARS format (WHEN/IF/WHILE patterns)
• Include correctness properties in the design that reference specific requirements
• Keep tasks small and focused so execution proceeds one task at a time
• Require explicit approval after each phase before advancing

Example use cases

• Add a new payment method: produce requirements.md, design.md, and tasks.md in .kiro/specs/new-payment-method/
• Refine a vague feature request into clear user stories with EARS acceptance criteria
• Document architecture and correctness properties for a critical subsystem before implementation
• Break a large feature into an ordered checklist of implementation tasks for sprint planning
• Detect current phase of an existing feature by checking for requirements.md / design.md / tasks.md