$ skilldirectory
— zsh — registry.skilldirectory.dev
skill library blog

home / Project Management / Spec Driven Workflow Skill by @alirezarezvani

Spec Driven Workflow Skill by @alirezarezvani

FREE
github stars★ 29,369updatedOct 2026repo@alirezarezvani
$git clone https://github.com/alirezarezvani/claude-skills

The skill is the engineering/skills/spec-driven-workflow folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.

Read the opening of the original SKILL.md
# 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.

### Why Spec-First Matters

1. **Eliminates rework.** 60-80% of defects originate from requirements, not implementation. Catching ambiguity in a spec costs minutes; catching it in production costs days.
2. **Forces clarity.** If you cannot write what the system should do in plain language, you do not understand the problem well enough to write code.
3. **Enables parallelism.** Once a spec is approved, frontend, backend, QA, and documentation can all start simultaneously.
…

Excerpt only, quoted from the author's repository. Open the repository for the complete file.