Spec-Driven Development (SDD) FAQs

Question 1

Can I revisit earlier phases once execution has started?

Accepted Answer

Yes. The workflow is iterative. If a snag is found during execution, the skill allows you to loop back to the design or planning phases to update the specification before resuming work.

Question 2

How does the spec-critic sub-agent work?

Accepted Answer

The spec-critic is a specialized agent that acts as a senior engineer. It performs adversarial reviews of your requirements and plans, challenging assumptions and identifying potential contradictions before execution begins.

Question 3

What is the difference between Interactive and High Agency mode?

Accepted Answer

Interactive mode prompts the user for confirmation at every phase. High Agency mode allows Claude to iterate through analysis, design, and critique autonomously, only stopping for user input if a genuine ambiguity occurs.

Question 4

What is Spec-Driven Development (SDD)?

Accepted Answer

SDD is a workflow where specifications act as the source of truth. Implementation follows strictly from these specs, ensuring that all code meets predefined requirements and architectural standards before being written.

Question 5

When should I use a compact spec vs. a directory spec?

Accepted Answer

Use a compact spec (single file) for small tasks with 1-2 requirements that can be finished in one session. Use a directory spec for complex features involving 3+ requirements, architectural decisions, or multi-session work.

Spec-Driven Development (SDD)

Key Features

Use Cases

Spec-Driven Development (SDD)

Key Features

Use Cases