sowadalmughni

Spec Driven Dev — Testing skill for Claude Code

Testing community

A Claude Code skill that blocks code generation until a PRD and Technical Architecture Spec exist and are approved.

How to install Spec Driven Dev

This entry records only its repository, not the path inside it, so there is no exact command to give. Open sowadalmughni/spec-driven-dev and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Spec Driven Dev does

A Claude Code skill that blocks code generation until a PRD and Technical Architecture Spec exist and are approved. Enforces a strict docs-first workflow: PRD, feature spec, architecture, then atomic implementation prompts with VERIFY commands.

Alternatives in Testing

AI Contribution Skills (Engram) — branch-pr: clean branch and PR workflow 2.5k ★
Spy — by spylang - Enforces strict coding conventions with comprehensive testing guidelines, multiple code compilati 678 ★
TDD Diagnostics.V1 — Follow strict TDD stages 272 ★

README

spec-driven-dev

A Claude Code skill that enforces architecture-first development before generating any implementation code.

**The problem it solves:** AI tools generate code faster than any human can type. But generating code is not the same as building software. A founder can spend 18 days building a product with AI assistance and end up with:

A database schema that is never connected to the application
Frontend pages that are fully styled but call no API
Backend modules that exist but have no entry points
Integrations that are mocked rather than wired
No cohesive data flow through the entire system

This skill prevents that. It halts code generation until a Product Requirements Document and Technical Architecture Spec exist and are approved. Every implementation task is then generated as an atomic prompt with explicit file paths, numbered tasks, and bash VERIFY commands.

Install

npx skills add https://github.com/sowadalmughni/spec-driven-dev

Or add to a project directly:

mkdir -p .claude/skills
git clone https://github.com/sowadalmughni/spec-driven-dev .claude/skills/spec-driven-dev

How It Works

The skill activates when you ask Claude Code to build, implement, generate, create, or write anything. Instead of producing code, it runs a four-phase workflow:

**Phase 0 — Scan.** Checks whether a spec already exists for the requested feature. If yes, resumes from the approved spec. If no, starts Phase 1.

**Phase 1 — PRD.** Generates a Product Requirements Document using the included template. Asks for approval before continuing. Does not write code.

**Phase 2 — Feature Spec.** Generates a component breakdown that bridges the PRD to the technical design. Names every component, its responsibility, and its explicit non-responsibilities. Asks for approval before continuing.

**Phase 3 — Architecture.** Generates a full Technical Architecture Spec: module structure, database schema, API contracts, end-to-end data