Kiro: Spec-Driven Development Workflow FAQs

Question 1

How do I trigger the Kiro skill?

Accepted Answer

You can activate Kiro by simply typing 'kiro' or by making reference to the '.kiro/specs/' directory in your conversation with Claude.

Question 2

What is the EARS format used in Kiro?

Accepted Answer

EARS (Easy Approach to Requirements Syntax) is a structured template for writing requirements (e.g., 'WHEN [event] THEN [system] SHALL [response]') to ensure they are clear, testable, and unambiguous.

Question 3

Can Kiro handle existing codebases?

Accepted Answer

Yes, Kiro is designed to follow existing patterns and write the absolute minimal code needed to fulfill the specific requirements of a new feature within your current project.

Question 4

Does Kiro implement features automatically?

Accepted Answer

No, Kiro follows a disciplined workflow. It first creates requirements and design documents for your approval, then generates a task list, and finally implements code one task at a time.

Question 5

Where does Kiro store my project specifications?

Accepted Answer

All generated documentation, including requirements.md, design.md, and tasks.md, is stored locally in your project under the '.kiro/specs/{feature-name}/' directory.

Kiro: Spec-Driven Development Workflow

关于

主要功能

使用场景

Kiro: Spec-Driven Development Workflow

关于

主要功能

使用场景