Spec-Driven Development

Fresh

Two structured approaches for planning before execution.

Choosing Your Approach

Approach	Best For	Commands
Spec-Kit	New features, greenfield projects	/speckit.*
OpenSpec	Iterative changes, existing codebases	/openspec.*

---

Spec-Kit Workflow

Step 1: Constitution

/speckit.constitution

Creates project principles at .specify/memory/constitution.md. Run once per project.

Step 2: Specify

/speckit.specify

Creates a detailed feature specification.

Step 3: Clarify (Repeat as Needed)

/speckit.clarify

Identifies gaps, asks up to 5 targeted questions. Run multiple times until the spec is solid.

Step 4: Plan

/speckit.plan

Converts the specification into an implementation plan.

Step 5: Tasks

/speckit.tasks

Breaks the plan into dependency-ordered tasks.

Step 6: Quality Check

/speckit.analyze    # Cross-artifact consistency
/speckit.checklist  # Requirements validation

Step 7: Generate Auto Run Documents

/speckit.implement

Outputs markdown checklists ready for Auto Run execution.

Optional: GitHub Issues

/speckit.taskstoissues

Converts tasks directly to GitHub Issues.

---

OpenSpec Workflow

Step 1: Propose

/openspec.proposal

Creates proposal.md, tasks.md, and spec deltas.

Step 2: Apply

/openspec.apply

Implements the approved proposal.

Step 3: Archive

/openspec.archive

Archives the completed change for reference.

Auto Run Integration

/openspec.implement

Generates Auto Run documents from the proposal.

---

Combined Workflow

Use Spec-Kit for the initial build, then OpenSpec for subsequent iterations and refinements.

See Also

• Slash Commands — Full command reference
• Auto Run Workflow — Execute generated documents
• Inline Wizard — Alternative to Spec-Kit