orcalisted

Triggered by the slash command "/orca path/to/plan.md". Takes a finalized project plan and executes it in parallel: splits it into independent task chunks, spawns coding agents in cmux panes (default 2 per wave, hard ceiling 4 — both constants live in SKILL-lib.sh; every wave size is confirmed by the user before spawning; each agent works in its own git worktree and branch), monitors progress via status.md, rebases each completed branch onto the default branch, fast-forwards it with --ff-only, auto-resolves simple conflicts, escalates complex ones to the user, and cleans up worktrees and branches once every wave is integrated. Use this skill whenever the user runs "/orca", or asks to "execute the plan," "run the plan in parallel," "spawn agents on this," "kick off multi-agent execution," "parallelize the build," or otherwise wants a finalized plan carried out using multiple coordinated coding agents.
orassayag/agentic-project-workflow · ★ 1 · AI & Automation · score 65

Install: claude install-skill orassayag/agentic-project-workflow

# Orca — Parallel Execution Orchestrator ## Invocation ``` /orca path/to/plan.md [review=off|light|full] ``` The argument is the path to the finalized plan file. It does not have to be named `plan.md` — any path works. If no argument is provided, default to `plan.md` in the project root. **`review` setting (default: `light`):** | Level | What happens | |-------|--------------| | `off` | No automated review. | | `light` (default) | At each wave's end, before declaring the wave done, the orchestrator runs the `/code-review` skill at **low** effort **once on the combined wave diff** (`git diff ${WAVE_START_SHA}..HEAD`) — one review per wave, never per-agent. Findings are surfaced to the user; fixes are their call. | | `full` | Everything in `light`, plus each agent's definition of done gains a review-only, domain-matched sub-agent self-review (see Phase 4c). Meant for production work, not the interview default. | **Important — resolving against `/plan`'s output:** Always check `docs/plans/<basename>.md` first; if it exists, use it (that's the version that went through `/plan`'s review loop). If only the raw path exists, warn the user before proceeding — they may be about to run an unreviewed draft. If neither path exists, stop and tell the user. You are the orchestrator. Your job is to read the plan file, decompose it into parallel-safe task chunks, spawn Cl