How this skill is triggered — by the user, by Claude, or both
Slash command
/spec-workflow:spec-driven-devThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The pipeline auto-continues between stages, pausing for user approval at each gate:
The pipeline auto-continues between stages, pausing for user approval at each gate:
SPEC ──review──▶ User Gate ──approve──▶ PLAN ──review──▶ User Gate ──approve──▶ IMPLEMENT ──review──▶ PR Ready
│ │ │
▼ ▼ ▼
Internal Internal Internal
Spec Review Plan Review PR Review
(mandatory) (mandatory) (mandatory)
| Command | Purpose |
|---|---|
/spec-workflow:spec <desc> | Run full pipeline (spec → plan → implement) |
/spec-workflow:plan <spec> | Generate PLAN.md with review (standalone) |
/spec-workflow:implement <plan> | Execute with PR review (standalone) |
/spec-workflow:review [spec] | Manual review trigger |
/spec-workflow:reset [flags] | Clear generated artifacts |
| Agent | SPEC | PLAN | PR | Codebase | Reasoning |
|---|---|---|---|---|---|
| SpecReviewer | [x] | - | - | No | No |
| Planner | [x] | Creates | - | [x] | - |
| PlanReviewer | [x] | [x] | - | No | No |
| Implementer | No | [x] | Creates | [x] | - |
| PRReviewer | [x] | No | [x] | No | No |
Ensures spec is evaluated as a standalone document for completeness and testability.
Catches plan drift - where plan misunderstood spec.
Forces plan adherence.
Prevents confirmation bias.
docs/specs/SPEC-{feature}.mddocs/plans/PLAN-{feature}.mddocs/reviews/REVIEW-SPEC-{feature}.mddocs/reviews/REVIEW-PLAN-{feature}.mddocs/reviews/REVIEW-PR-{feature}.mddocs/reviews/REVIEW-{pr-number}.mdClear generated artifacts to start fresh:
/spec-workflow:reset --dry-run # Preview deletions
/spec-workflow:reset --force # Delete all (no prompt)
/spec-workflow:reset --feature dark-mode # Scope to one feature
Clears SPEC-*.md, PLAN-*.md, REVIEW-*.md. Preserves .gitkeep.
npx claudepluginhub bryceewatson/bryce-labs-toolkit --plugin spec-workflowOrchestrates spec-driven development by triggering stage agents (CREATE, PLAN, IMPLEMENT, REVIEW, TEST). Manages spec files, AI-section edits, per-stage git commits. Activates on 'spec' keywords or /spec.
Drives a spec-driven workflow for multi-step features: specify requirements, research decisions, plan numbered slices, implement, then verify. Creates a reviewable paper trail in plans/<feature>/.
Executes GitHub Spec Kit's 5-phase workflow—constitution, specification, planning, task breakdown, implementation—from feature requests or resumes prior phases.