Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From flywheel
Coordinates parallel AI agents for coding tasks using role-based patterns (planner, coder, reviewer, QA), git branch isolation, and merge strategies with rebase and conflict resolution.
npx claudepluginhub romanticamaj/flywheel --plugin flywheelHow this skill is triggered — by the user, by Claude, or both
Slash command
/flywheel:multi-agentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Each agent has a **role** and a **stop condition**. This is structured coordination, not "many terminals."
Orchestrates multi-agent work at scale: research swarms, parallel feature builds, wave-based dispatch, and build-review-fix pipelines for tasks requiring 3+ agents.
Executes implementation plans by dispatching fresh subagents per task with dependency analysis, concurrent execution, and built-in two-stage self-review for spec compliance and code quality.
Orchestrates parallel AI coding agents in isolated Git worktrees using Agency CLI. Create, list, merge tasks; attach files; manage tmux sessions for simultaneous coding.
Share bugs, ideas, or general feedback.
Each agent has a role and a stop condition. This is structured coordination, not "many terminals."
Orchestrator (human)
+-- Planner agent(s) — produce spec + checklist
+-- Coding agent(s) — one feature each, parallel on separate branches
+-- Review agent(s) — review completed features
+-- QA agent — E2E verification
flywheel-config.json's branch_naming pattern (default: feat/{id}-{slug}).When parallel agents complete their features:
| Step | Action | Detail |
|---|---|---|
| 1 | Orchestrator decides merge order | Review completed branches; pick order based on dependencies and conflict likelihood |
| 2 | Rebase onto main | Each feature branch rebases onto latest main before merging. Keeps history linear. |
| 3 | Conflict resolution | If rebase conflicts arise, the Coding Agent for that feature resolves them in a new session (reads handoff log, sees conflict, resolves, re-runs smoke test) |
| 4 | Handoff log consistency | Each branch has its own claude-progress.jsonl entries. On merge, entries are appended to main's log in merge order. |
| 5 | Checklist consistency | feature-checklist.json on main is source of truth. Feature branches update their own feature's status only. On merge, checklist is updated on main. |
| Tool | Install | What it provides |
|---|---|---|
| gstack | git clone gstack repo | /plan-ceo-review, /plan-eng-review, /review, /qa, /ship + Conductor for parallel sprints |
| superpowers | Already a Claude Code plugin | dispatching-parallel-agents, subagent-driven-development, peer-reviewer agent |
| Claude Code native | Built-in | --worktree for isolation, Agent tool with subagent_type for parallel dispatch |
| Framework | How to detect |
|---|---|
| gstack | gstack commands in available skills |
| superpowers | dispatching-parallel-agents skill present |
| Native | Always available |