Spec-Driven Development (SDD) FAQs

Question 1

How does the PLANNING file protect my project?

Accepted Answer

The PLANNING file acts as a lock during the specification phase. It alerts Claude not to start implementation prematurely, especially during AutoCompact events which might otherwise cause the AI to lose track of the planning context.

Question 2

Why are system diagrams mandatory in this skill?

Accepted Answer

System diagrams, including state machine and data flow diagrams, are required to ensure the implementation is architecturally sound and that all edge cases in logic and data movement are accounted for.

Question 3

What happens during the Codex review loop?

Accepted Answer

Once an implementation plan is generated, the skill triggers an automated review by Codex to identify ambiguities or risks. It can run up to five corrective loops to refine the plan until it meets quality standards.

Question 4

What is Spec-Driven Development (SDD) in Claude Code?

Accepted Answer

SDD is a specialized skill that enforces a 'plan-first' approach, ensuring that requirements are clarified, the codebase is explored, and implementation plans are reviewed before any code changes occur.

Question 5

When should I use the spec-driven-dev skill?

Accepted Answer

It is best used for significant feature additions, component creations, or complex refactors where jumping straight into code would likely lead to technical debt or logic errors.

Spec-Driven Development (SDD)

Spec-Driven Development (SDD)

주요 기능

사용 사례

주요 기능

사용 사례