Pimzino/claude-code-spec-workflow

Automated workflows for Claude Code. Features spec-driven development for new features (Requirements → Design → Tasks → Implementation) and streamlined bug fix workflow for quick issue resolution (Report → Analyze → Fix → Verify).

About the project

Claude Code Spec Workflow is a collection of automated workflows that guides Claude Code through feature development and bug fixing. Developers use it to move from requirements to design, tasks, and implementation, or from a bug report through analysis, fixing, and verification, with the catalogue providing its commands and specialized agents.

This repository also configures its own agents. See what claude-code-spec-workflow tells them →

3.9kStars on the repository
14Mods indexed here, across every type
1y agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

Pimzino/claude-code-spec-workflow

Agent Claude Code

Design validation specialist. Use PROACTIVELY to validate design documents for technical soundness, completeness, and alignment before user review.

not rated 3.9k +2 1y ago A 30 tokens original MIT

Pimzino/claude-code-spec-workflow

Agent Claude Code

Requirements validation specialist. Use PROACTIVELY to validate requirements documents for completeness, clarity, and quality before user review.

not rated 3.9k +2 1y ago A 30 tokens original MIT

spec-task-executor

03

Pimzino/claude-code-spec-workflow

Agent Claude Code

Implementation specialist for executing individual spec tasks. Use PROACTIVELY when implementing tasks from specifications. Focuses on clean, tested code that follows project conventions.

not rated 3.9k +2 1y ago A 36 tokens original MIT

spec-task-validator

04

Pimzino/claude-code-spec-workflow

Agent Claude Code

Task validation specialist. Use PROACTIVELY to validate task breakdowns for atomicity, agent-friendliness, and implementability before user review.

not rated 3.9k +2 1y ago A 34 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: