HarnessCommunity★ 3.8k

Pimzino Spec Workflow

Updated Jul 5, 2026

An npm package that installs 10 slash commands (5 spec workflow + 5 bug fix), 4 specialized agents, a real-time dashboard, and steering documents into Claude Code. Spec workflow: /spec-create gates the agent through Requirements → Design → Tasks → Implementation. Bug fix workflow: /bug-create → /bug-analyze → /bug-fix → /bug-verify.

View on GitHub

What it does

/spec-create feature-name "Description"
Run the complete spec workflow: Requirements → Design → Tasks → auto-generated implementation commands.
/spec-execute task-id feature-name
Execute a specific task from the approved spec with full steering + specification context loaded.
/spec-steering-setup
Create product.md, tech.md, and structure.md as persistent project context that reduces repeated explanations.
/bug-create issue-name "Description"
Document a bug in structured format as the starting point for the /bug-analyze → /bug-fix → /bug-verify workflow.
claude-spec-dashboard
Real-time WebSocket dashboard for tracking spec and bug fix progress, with optional secure tunnel for stakeholder sharing.

Files (1)

OVERVIEW.mdprimary · markdown · 2.2 KB

## What it does

An npm package that installs a complete spec-driven development system into Claude Code: 10 slash commands, 4 specialized agents, a real-time dashboard, and steering documents that provide persistent project context.

**Spec workflow (new features):**

`/spec-create feature-name "Description"` — runs the complete workflow in one command:
1. Requirements → user stories and acceptance criteria
2. Design → technical architecture
3. Tasks → atomic agent-friendly task breakdown
4. Commands → auto-generated per-task slash commands (optional)

Then execute tasks individually with `/spec-execute 1 feature-name` or the auto-generated `/feature-name-task-1`.

**Bug fix workflow:**

| Command | Purpose |
|---------|---------|
| /bug-create issue-name "Description" | Document the bug with structured format |
| /bug-analyze | Investigate root cause |
| /bug-fix | Implement targeted solution |
| /bug-verify | Confirm resolution |

**Steering documents (persistent project context):** /spec-steering-setup creates product.md (vision, target users, key features), tech.md (stack, tools, constraints), and structure.md (file organization, naming conventions). Claude reads these at session start for consistent code generation without repeated explanations.

**4 specialized agents:** spec-task-executor, spec-requirements-validator, spec-design-validator, spec-task-validator. All optional — everything works with built-in fallbacks.

**Real-time dashboard:**

```bash
npx -p @pimzino/claude-code-spec-workflow claude-spec-dashboard
```

Live progress tracking via WebSocket with git integration. Optional tunnel for sharing with external stakeholders.

**Context optimization:** 60–80% token reduction via bulk document loading (get-steering-context, get-spec-context, get-template-context) and session-based caching.

## Install

```bash
npm i -g @pimzino/claude-code-spec-workflow
claude-code-spec-workflow          # run setup in your project directory
```

Restart Claude Code. The /spec-* and /bug-* commands are immediately available.

**Tip:** Use Opus for /spec-create (spec generation) and Sonnet for /spec-execute (implementation) for best cost-to-quality ratio.