Template Bridge Plugin
Unified development workflow for Claude Code: Superpowers + Beads + Templates.
Bridges three powerful Claude Code plugins into a single disciplined workflow with on-demand access to 413+ specialist agent templates.
Prerequisites
| Plugin | Install | Purpose |
|---|
| Superpowers | /plugin install superpowers | TDD, brainstorming, debugging, code review |
| Beads | /plugin install beads | Task tracking across sessions |
Both are optional — the workflow skill adapts, but you get the full power with all three.
What's Inside
| Component | Type | Purpose |
|---|
unified-workflow | Skill | How to work: beads task → brainstorm → plan → TDD → review → finish |
template-catalog | Skill | 413+ specialist agents on-demand from claude-code-templates |
browse-templates | Command | /browse-templates — manual template search |
The Stack
┌─────────────────────────────────────────────────────┐
│ YOUR TASK │
├──────────┬──────────────────┬───────────────────────┤
│ Beads │ Superpowers │ Template Bridge │
│ WHAT │ HOW │ WHO │
│ │ │ │
│ bd create│ brainstorming │ template-catalog │
│ bd ready │ writing-plans │ 413+ specialist agents│
│ bd close │ TDD (red-green) │ on-demand install │
│ │ debugging │ │
│ │ code-review │ │
│ │ verification │ │
└──────────┴──────────────────┴───────────────────────┘
The Flow
Every task follows this sequence:
1. TASK bd create -t feature "..." or bd update <id> --status in_progress
│
2. BRAINSTORM superpowers:brainstorming → design before code
│
3. PLAN superpowers:writing-plans → 2-5 min tasks
│
4. ISOLATE superpowers:using-git-worktrees (non-trivial work)
│
5. IMPLEMENT For each task:
├─ RED: write ONE failing test
├─ VERIFY: confirm it fails for the right reason
├─ GREEN: minimal code to pass
├─ VERIFY: all tests pass
├─ REFACTOR: clean up
└─ COMMIT
│
6. REVIEW superpowers:requesting-code-review
│
7. VERIFY superpowers:verification-before-completion
│
8. FINISH superpowers:finishing-a-development-branch
│
9. CLOSE bd close <id> --reason "Done"
TDD: Red-Green-Refactor
No production code without a failing test first. Ever.
RED ──────► VERIFY RED ──────► GREEN ──────► VERIFY GREEN ──────► REFACTOR ──────► COMMIT
write test fails for minimal all tests clean up after each
right reason code pass green
Debugging
Always invoke superpowers:systematic-debugging BEFORE any fix:
- Root cause — read errors, reproduce, check recent changes
- Pattern analysis — find working examples, compare
- Hypothesis — single-variable test
- Fix — with failing test first
- Stop after 3 failed attempts → question architecture
Verification Gate
Before claiming anything done:
- Identify the proving command
- Run it fresh
- Read complete output + exit code
- Verify it supports the claim
- Only then claim done
"Evidence before claims, always."
External Templates
When a task needs a specialist not in current skills:
# Direct install (always fresh from repo)
npx claude-code-templates@latest --agent security/security-auditor --yes
# Interactive browser
npx claude-code-templates@latest
Categories (26)
