superteam
Four superpowers-disciplined Claude Code subagent definitions for running a TDD-driven feature-development pipeline as a native Agent Team. Multiplexer-agnostic — runs under cmux, tmux, iTerm2's split panes, or in-process (spawned via the Agent tool, no multiplexer pane per teammate; full lifecycle still works).
This plugin ships nothing but four agent definitions and one setup wizard. All the infrastructure — task list, dependency resolution, display panes, lifecycle hooks — comes from native Claude Code. The agent definitions encode the workflow on top: a planner that breaks features into tickets, an implementer that obeys red-green-refactor and verification-before-completion, and two reviewers that score against the spec and the code.
Quickstart
# 1. Install the plugin
claude /plugin marketplace add AhmedElBanna80/superteam
claude /plugin install superteam
# 2. Run the setup wizard (choose multiplexer + model per agent)
claude /superteam:setup
# 3. Follow the launch command the wizard prints. Then tell the lead:
You are running as the superteam lead. Spawn superteam-implementer,
superteam-spec-reviewer, and superteam-code-reviewer as my team.
Then process ticket AUTH-1: "add login form with email validation. Use TDD."
That's it. The lead provisions a per-ticket worktree, drops three tasks into the shared list with dependencies, and the teammates self-claim and execute.
Roadmap
Active work and known findings are tracked as GitHub Issues with a Kanban view:
Labels:
f-finding — live-run findings (F1–F12)ticket — feature workdiscipline — agent prompt / process rulesv0.4 (shipped) / v0.5 (planned)status:done / status:in-progress / status:todo
The Project board filters by status label and provides Todo / In Progress / Done columns. Closed issues link back to the PR that shipped them.
The four agents
| Agent | Role | Tools | Default model |
|---|
superteam-planner | Lead. Provisions per-ticket worktrees, writes rich task descriptions, runs superpowers:finishing-a-development-branch when each ticket clears. | Read, Grep, Glob, Bash, TodoWrite | opus |
superteam-implementer | Self-claims impl(...) tasks. References superpowers:test-driven-development + verification-before-completion. Hook bypass forbidden. | Read, Write, Edit, Bash, Grep, Glob, NotebookEdit | sonnet |
superteam-spec-reviewer | Self-claims spec-review(...) tasks. Read-only. Verifies against the original spec. | Read, Grep, Glob, Bash | sonnet |
superteam-code-reviewer | Self-claims code-review(...) tasks. Read-only. Quality, security, conventions, TDD assessment, hook-bypass check. | Read, Grep, Glob, Bash | sonnet |
Each agent definition references the relevant superpowers skills rather than embedding them, so discipline stays in one place and updates upstream automatically. The /superteam:setup wizard lets you override the default model per agent.
Planner subagent mode
When the planner is invoked via the Agent tool from another Claude session (rather than as a top-level claude --agent superteam-planner), it cannot open multiplexer panes — tasks would sit pending indefinitely. The planner detects this automatically on startup:
- Env-var check — if
CLAUDE_SUBAGENT=1 or CLAUDE_AGENT_ID is set, the planner classifies the session as a subagent.
- Pane-count fallback — after
TeamCreate, if the configured multiplexer reports 0 panes, the planner infers it is running in-process and falls back to the Agent tool for spawning.
In subagent mode the planner prints:
Running in subagent mode — teammates spawn in-process, no multiplexer pane per teammate; full lifecycle still works.
In-process means there is no visible split-pane per teammate — the teammate shares this session — but all tasks are created, claimed, and completed in the normal impl → spec-review → code-review sequence. (Under cmux or tmux the same Agent call would have been rendered as a native split or window instead.) Use this mode when superteam is itself a step inside a larger orchestration.
The ticket command
/superteam:ticket <id> <raw-spec> is a structured ticket-intake command for the planner. It runs four phases automatically:
