Where does Kiro store the specification files?

Kiro creates a standardized directory at .kiro/specs/{feature-name}/ within your repository to store requirements.md, design.md, and tasks.md.

What triggers the Kiro workflow?

You can activate the skill by using keywords like 'kiro', 'feature spec', '需求文档' (requirements document), or by referencing the '.kiro/specs/' directory.

Does Kiro support test-driven development?

Yes, Kiro's philosophy is rooted in TDD. It prioritizes creating automated tests and writing the absolute minimal code necessary to satisfy the requirements.

Can Kiro implement features automatically?

Kiro follows a phased approach. It first requires approval on requirements and design before generating a task list. Once the plan is approved, you can ask Claude to execute tasks one by one.

What is the EARS format used by Kiro?

EARS stands for Easy Approach to Requirements Syntax. It is a structured template Kiro uses to write clear, non-ambiguous requirements based on events, conditions, and system responses.

Kiro Spec-Driven Workflow

Name: Kiro Spec-Driven Workflow
Author: tianzecn

bytianzecn

Productivity & Workflow

Guides developers through an interactive, spec-driven development process from initial idea to test-driven implementation.

About

Kiro is a specialized development companion for Claude Code designed to bring structure to the creative coding process. It transforms raw feature ideas into comprehensive technical specifications by following a rigorous four-phase workflow: requirements gathering using the EARS syntax, architectural design, granular task planning, and disciplined implementation. By enforcing a 'plan-before-code' philosophy and a test-driven approach, Kiro ensures that developers build scalable, well-documented features while maintaining a minimal and clean codebase.

Key Features

0 GitHub stars
Automated generation of detailed design documents including architecture and data models
Precision task execution focusing on minimal code and test-driven development (TDD)
Standardized project organization within a dedicated .kiro/specs/ directory
Interactive requirements gathering using the EARS (Easy Approach to Requirements Syntax) format
Incremental implementation planning with checkbox-based task lists in Markdown

Use Cases

Maintaining architectural integrity in complex projects through mandatory design phases
Transforming vague feature ideas into structured technical requirements and implementation plans
Executing systematic, test-first code updates for new or existing features

About

Key Features

0 GitHub stars
Automated generation of detailed design documents including architecture and data models
Precision task execution focusing on minimal code and test-driven development (TDD)
Standardized project organization within a dedicated .kiro/specs/ directory
Interactive requirements gathering using the EARS (Easy Approach to Requirements Syntax) format
Incremental implementation planning with checkbox-based task lists in Markdown

Use Cases

Maintaining architectural integrity in complex projects through mandatory design phases
Transforming vague feature ideas into structured technical requirements and implementation plans
Executing systematic, test-first code updates for new or existing features