Enforce structured dev workflows with Beads for task tracking and dependencies, Superpowers for brainstorm/plan/TDD/review cycles, and git worktrees for isolation. Proactively suggest, browse, search, and install 413+ specialist agent templates from claude-code-templates for niche expertise in blockchain, game dev, data science, Kubernetes, Rust/Go, databases, and video processing.
npx claudepluginhub maslennikov-ig/template-bridge --plugin template-bridgeProactively suggest and install specialist agent templates from claude-code-templates (413+ agents, 26 categories). TRIGGER: When a task needs a specialist agent NOT available in current skills/agents. Examples: blockchain, game dev, data science, Kubernetes, database optimization, Rust/Go experts, video processing.
Unified development methodology: Superpowers + Beads + Templates. TRIGGER: At session start, before any task, or when workflow is unclear. Defines the mandatory flow: beads task → brainstorm → plan → TDD → review → finish.
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimCore skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Opinionated workflow skills. Hard gates, not suggestions. Spec through blueprint, implementation, verification, and shipping -- the skills refuse to let you skip steps.
Unified toolkit for Context-Driven Development with spec-first planning, TDD workflow, and Beads integration
Agentic development framework for Claude Code — disciplined workflow routing, TDD enforcement, safety hooks, systematic debugging, and code review
Battle-tested Claude Code plugin for engineering teams — 53 agents, 203 skills, 69 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
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.
| 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.
| 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 |
┌─────────────────────────────────────────────────────┐
│ 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 │ │
└──────────┴──────────────────┴───────────────────────┘
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"
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
Always invoke superpowers:systematic-debugging BEFORE any fix:
Before claiming anything done:
"Evidence before claims, always."
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