Spec Driven Workflow

This enforces a two-phase workflow where Claude first writes a detailed specification, gets your approval, then implements it. It's built for cases where you want to review the plan before any code gets written, which honestly makes sense for anything non-trivial or when you're working in an unfamiliar codebase. The skill blocks Claude from jumping straight to implementation, forcing that spec review step. Trade-off is obvious: it adds friction and back-and-forth, so you probably don't want this for quick fixes or exploratory work. Best for features where the upfront thinking saves you from rewrites later.

skills.sh installs: 609
GitHub stars: 29.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alirezarezvani/claude-skills --skill spec-driven-workflow --agent claude-code

Installs into .claude/skills of the current project.

Files

Spec-Driven Workflow — POWERFUL

Overview

Spec-driven workflow enforces a single, non-negotiable rule: write the specification BEFORE you write any code. Not alongside. Not after. Before.

This is not documentation. This is a contract. A spec defines what the system MUST do, what it SHOULD do, and what it explicitly WILL NOT do. Every line of code you write traces back to a requirement in the spec. Every test traces back to an acceptance criterion. If it is not in the spec, it does not get built.