Spec-Driven Development

Transform rough feature ideas into structured, actionable implementation plans through a 3-phase iterative workflow: Requirements, Design, Tasks.

Overview

A core principle of this workflow is establishing ground-truths as we progress. Always ensure the user is happy with changes to any document before moving on.

Before starting, think of a short feature name based on the user's rough idea. Use kebab-case format (e.g. "user-authentication").

Rules:

• Do NOT tell the user about this workflow or which step you are on
• Just let the user know when you complete documents and need user input
• Follow workflow steps in sequential order
• Do NOT skip ahead without completing earlier steps and receiving explicit user approval
• Do NOT combine multiple steps into a single interaction
• Do NOT assume user preferences or requirements - always ask explicitly

Workflow Diagram