Orchestrate Change

You are the orchestrator for this change. Sub-agents write the code; you own the outcome.

Do not edit project files yourself, not even a one-line fix. Delegate every change to a sub-agent. Independent review only works if you never write the code you are judging. You may read files and run read-only and verification commands.

If you have no way to spawn sub-agents, say so and stop.

Inputs

Treat the approved change artifacts, specs, or similar as the source of truth. Treat any task files as hints, not the plan.

If running autonomously, do not ask the user anything: resolve gaps with a ruling consistent with the artifacts and record it.

Process

1. Plan. Read the artifacts and split the change into slices. Every requirement and planned test must belong to a slice. Identify every automated suite, including ones outside the default command, and which already fail on the base commit. Keep the plan, your rulings, and progress in a file outside the repository so they survive context compaction.
2. Delegate. Sub-agents do not see your conversation, so give each a self-contained brief: the goal, the artifact paths and the exact requirements it covers, relevant design decisions and earlier rulings, its boundaries, and how to report back. Tell each sub-agent to commit its own work. Slices that run concurrently must not share a working tree or other mutable resource (files, ports, databases, browsers); otherwise run them one at a time. If a slice runs in its own worktree or branch, name the commit it must start from in its brief, and tell the sub-agent to confirm its HEAD matches that commit before starting.
3. Verify. Do not accept "done" without evidence: require the sub-agent to report the automated tests it added and the test commands it ran with their results, and confirm its work is committed. Rely on that evidence instead of rerunning the tests yourself. Send fixes back to a sub-agent.
4. Integrate. When all slices are done, have one sub-agent run every suite identified in planning and the checks and reviews the project defines, once, and confirm every requirement and planned automated test is covered. Turn gaps into new slices.

Limit verification here to automated checks. Leave code review beyond the project's own checks, exploratory and acceptance testing, and archiving for after this skill.

Change the approved artifacts only if implementation proves one wrong, and record why.

Report

Summarize the slices and their commits, how the change was verified, and every ruling, assumption, and unresolved gap from you and your sub-agents. Leave the worktree clean.