Kiro Skill

Transforms vague feature ideas into complete specifications through a three-phase workflow: requirements in EARS format (structured acceptance criteria with WHEN/THEN statements), design documents with architecture diagrams, and test-driven task lists. Creates everything in a .kiro/specs directory with kebab-case naming. The workflow is interactive and gated, meaning it won't move from requirements to design, or design to tasks, without your explicit approval. Built for developers who want structure without the ceremony of heavyweight project management tools. The task generation specifically focuses on incremental, testable steps while excluding deployment, user testing, and anything non-code related. Works well if you think in user stories and want a lightweight spec-driven approach.