board-superpowers

board-superpowers

An enforcement layer that makes parallel AI execution behave like a real team instead of chaos.

Built as a plugin for Claude Code and OpenAI Codex CLI. Composes superpowers (TDD, code review, debugging) and gstack (design, QA, security) — does not replace them.

English · 简体中文

---

Why this exists

The AI-era architect's primary value is no longer writing code. It is sequencing problems, designing architecture, judging tradeoffs, and verifying that what the AI built actually works. Coding itself is becoming AI's job.

board-superpowers operationalizes that role-shift. Concretely:

• You run N parallel Consumer sessions against one Manager session.
• You walk away.
• You come back to a merge-ready queue of PRs, each carrying an explicit ## Human Verification TODO checklist.
• Verifying that checklist is your remaining job — and the plugin's whole shape is designed to maximize how far that scarce attention can go.

If you have personally decided to focus on judgment and architecture rather than line-by-line authorship, and you are willing to dispatch implementation to AI without babysitting it — this plugin is for you.

What changes for you

Without board-superpowers	With board-superpowers
One terminal, babysit one session, rebase constantly	N terminals, each a dedicated Consumer you mostly do not read
"What should I work on?" lives in your head	A Manager session reads the board and tells you
Sprint planning is a lossy conversation	Decomposition is a skill that enforces INVEST and vertical slicing
Scope creep caught mid-PR	Scope is frozen into the card body before any Consumer claims it
Merges are surprises	Every PR ships with a structured ## Human Verification TODO
Your coordination state is in your head	Your coordination state is your own GitHub Project — we never own it

The three pillars

board-superpowers sits at the intersection of three commitments. Most adjacent tools cover one or two; covering all three is the differentiation.

1. Substrate commitment — your board, never ours

Truth lives on your existing board (GitHub Project today; Linear, Jira, others via the BoardAdapter contract tomorrow). We never own a hosted control plane, never run a backend, never ask you to log into our service.

If a feature ever requires durable state that lives anywhere except your board + your git remote, we have broken the commitment. This is structural, not aspirational — it is what makes us the open-source choice next to Devin / Factory / similar hosted products that must own their state for business reasons.

2. Methodology embedded as code

The agile discipline is enforced by the plugin, not configured by you:

• INVEST every card. Independent, Negotiable, Valuable, Estimable, Small, Testable.
• Vertical slices over layer-splits. Always.
• Pull-based work: Consumers claim atomically; Managers do not assign.
• One PR per session. No multi-card sessions.
• Lightweight retro — aggregated from PR notes, not a separate ceremony.
• Soft WIP limit (default 5) — warn, do not block.
• Cards are XS / S / M / L — never story points, never velocity, never per-architect KPIs.

Anything that smells like sprint-cadence-cosplay (story-point estimation, velocity tracking, retro-as-meeting) is deliberately absent. AI orchestration inverts which resources are scarce, and most ceremonies that human teams need are noise here.

3. Composition is permanent

board-superpowers never reimplements TDD, QA, code review, brainstorming, or security audit. Those belong to superpowers and gstack. board-superpowers is the scheduling layer that composes them into routines:

• Manager's intake routine routes through gstack:/office-hours and superpowers:brainstorming.
• Consumer's implementation routine delegates to superpowers:subagent-driven-development.
• Consumer's pre-PR verification chain calls superpowers:verification-before-completion → superpowers:requesting-code-review → gstack:/review → gstack:/codex (cross-platform adversarial review) → gstack:/qa (UI cards) → gstack:/cso (security-flagged cards).

If a similar discipline already exists in those upstream plugins, we use it. If we ever ship a duplicate, that is a bug.

The two roles

Every session plays exactly one role with respect to the kanban. Routing happens automatically based on your first message.

Producer — keep-the-board-healthy session

Today's only Producer-class role: Manager.

A Manager session is long-lived, aggregate-view, never writes code. It exposes 15 capabilities across five clusters: