orchestrate-devlisted

Use when an implementation request is bigger than one unit of work — a spec or plan file, a multi-part feature, a review doc with several items, 'implement all of this', 'build X end to end', 'do these N things', 'orchestrate this', 'run these in parallel', 'split this across agents'. Plans a dependency-aware task graph, runs each task under a role (parallel workers where supported, sequentially where not), integrates onto ONE objective branch, and delivers ONE PR. A single small change is not orchestration — that falls through to start-dev.
Tamircohen28/tamirs-superpowers · ★ 2 · AI & Automation · score 74

Install: claude install-skill Tamircohen28/tamirs-superpowers

# orchestrate-dev Turn one user objective into a task graph, run it, integrate it, and deliver **one PR**. Role contract: [`core/roles/orchestrator.md`](../../../core/roles/orchestrator.md). Policies inherited, never restated here: [`core/policies/safety.md`](../../../core/policies/safety.md), [`core/policies/git.md`](../../../core/policies/git.md), [`core/policies/validation.md`](../../../core/policies/validation.md), [`core/policies/delivery.md`](../../../core/policies/delivery.md). ## The two separations that make this work | Separation | Meaning | |---|---| | Objective ≠ task | The user asked for one thing. It is *executed* as several. | | Work unit ≠ delivery unit | A task ends at **commit + handoff**. Only the objective ends at a PR. | | Role ≠ provider | A task needs an implementer; whichever harness is available plays that role. | **Validation tier: 2 (integration).** This skill runs the integration gates. Tier 1 belongs to `worker-dev`; Tier 3 belongs to CI via `pr-dev`. ## Step 0 — decide whether to orchestrate at all Orchestration has real cost: branches, worktrees, state files, an integration pass. Do not pay it for a small change. Fall through to `start-dev` (single worker + delivery) when **all** of these hold: - one coherent change, plausibly one commit or a short series; - one write scope — no two independent areas of the tree; - no ordering constraint between sub-parts; - no separate specialist pass genuinely needed (tests written alongside is not a