Multi-Phase Orchestrator (Beta)

Status: beta. Do not invoke this skill implicitly. Use it only when the user explicitly names $multi-phase-orchestrator or directly asks to use this skill.

Coordinate multiple work units by creating fresh Codex worktree threads, giving each thread a narrow packet, monitoring them, verifying their outputs, and integrating completed work safely. A work unit can be a plan phase, bug finding, PR comment, review finding, adversarial-gate slice, docs task, validation task, or integration fix.

This skill is an orchestration layer. It does not replace the skills or workflows used inside each unit; it routes them explicitly.

Operating Model

Start from the work source the user gives. Do not invent a default source hierarchy. Valid sources include, but are not limited to:

• a user-provided plan
• a named review or bug-finding skill whose output should become work units
• a set of PR comments or review threads named by the user
• a list of phases, slices, milestones, or tasks
• a prior run the user explicitly names

If the user has not provided a source that can produce work units, ask for the source or ask whether to run a named discovery/review skill first.