spec-driven-workflow
Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.
Profile →npx skills add alirezarezvani/claude-skills --skill spec-driven-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. 4. **Creates accountability.** The spec is the definition of done. No arguments about whether a feature is "complete" — either it satisfies the acceptance criteria or it does not. 5. **Feeds TDD directly.** Acceptanc
- Overview
- Why Spec-First Matters
- The Iron Law
- The Spec Format
- Mandatory Sections
- RFC 2119 Keywords
- Bounded Autonomy Rules
- STOP and Ask When:
- Continue Autonomously When:
- Escalation Protocol
- Workflow — 6 Phases
- Phase 1: Gather Requirements
- Phase 2: Write Spec
- Phase 3: Validate Spec
python spec_validator.py --file spec.md --strict python test_extractor.py --file spec.md --framework pytest --output tests/ Generate a spec template python spec_generator.py --name "User Authentication" --description "OAuth 2.0 login flow" Validate a spec python spec_validator.py --file specs/auth.md --strict Extract test cases python test_extractor.py --file specs/auth.md --framework pytest --output tests/test_auth.py
What does the spec-driven-workflow skill do?
Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill spec-driven-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.