Spec-Driven Development (Specify) FAQs

Question 1

Does this skill help with Architectural Decision Records (ADRs)?

Accepted Answer

Yes, Specify includes a dedicated phase for synthesizing decisions into ADRs, which are stored in the project's documentation for historical context.

Question 2

What is the primary output of the Specify skill?

Accepted Answer

The primary outputs are a human-readable Spec Packet for documentation and a machine-readable Capability Map used by the /plan command to decompose work into tasks.

Question 3

Can I use existing PRDs or design docs with this skill?

Accepted Answer

Absolutely. During the initialization phase, you can point Specify to existing reference materials, and it will extract context to pre-fill the scope and clarification phases.

Question 4

Why does Specify focus on 'invariants before architecture'?

Accepted Answer

This principle ensures that the software's behavior and constraints are fully understood before implementation details are discussed, preventing rework caused by architectural assumptions.

Question 5

How does Specify handle session interruptions?

Accepted Answer

Specify automatically detects session state in the .tasker directory. If a session is interrupted, it uses an auto-resume protocol to jump back to the exact phase and step where you left off.

Spec-Driven Development (Specify)

Key Features

Use Cases

Spec-Driven Development (Specify)

Key Features

Use Cases