kiro-skill_skill

Overview

This skill guides an interactive spec-driven development workflow from idea to implementation plan. It generates EARS-formatted requirements, design documents, and test-driven task lists, storing artifacts in .kiro/specs/{feature-name}/. It enforces sequential phases and explicit approval before moving forward.

How this skill works

Invoke the skill with triggers like "kiro", "feature spec", or ".kiro/specs/" to start. It drafts requirements.md (EARS acceptance criteria and user stories), produces design.md (architecture, components, data models, testing strategy) after requirements approval, and creates tasks.md (numbered, test-focused implementation tasks) once design is approved. All phases stop for user review and require explicit approval before proceeding.

When to use it

• Converting a product idea into a formal feature spec
• Defining clear acceptance criteria using EARS syntax
• Creating a design document informed by targeted research
• Breaking design into test-driven implementation tasks
• Preparing a single, focused task for execution

Best practices

• Use kebab-case feature names and store files under .kiro/specs/{feature-name}/
• Create complete requirements first; do not start design until requirements are approved
• Keep tasks incremental and test-driven; prefer minimal code per step
• Document architectural decisions and cite research when needed
• Always ask for explicit approval after each phase before progressing

Example use cases

• Turn a rough idea like "social login" into requirements.md with EARS acceptance criteria
• Generate design.md with component diagrams and API contracts for a payments feature
• Produce tasks.md that breaks implementation into testable sub-tasks (2.1, 2.2 style)
• Request execution of a single documented task and receive a minimal-code implementation
• Audit .kiro/specs/ to determine current phase for a given feature