claude-code

Plan and decompose a large development Epic into a coherent overall design plus PR-sized, dependency-ordered tasks that multiple autonomous runners implement in parallel. Use this whenever the user wants to break a big feature/project/initiative into tasks, set up parallel or multi-agent development, orchestrate several Claude runners, define an epic, or says things like 'plan this epic', 'break this down into tasks', 'set up the epic', 'decompose this work', 'epic:plan', or hands you a large spec/PRD and wants it turned into an executable plan. This is the orchestrator's planning half and pairs with epic:run. Prefer this over ad-hoc task lists whenever the work is large enough to span multiple PRs or multiple workers.

Autonomously pick up and implement Epic tasks one at a time from inside a git worktree: claim a ready task, write a spec, get it auto-reviewed, implement it, open a PR, block until it is merged, then immediately take the next task — never stopping until every reachable task is done. Use whenever the user wants to run an epic, start or continue an epic runner, work epic tasks in parallel, join an epic as a worker, or says things like 'epic:run', 'run the epic', 'start a runner', 'take a task', 'work the epic'. This is the orchestrator's execution half and pairs with epic:plan. It MUST run inside a worktree and coordinates with other runners through the shared .epic/ state.