orchestrating-developmentlisted

# Orchestrating Development Drive an approved spec through plan → plan review → batched implementation → whole-branch code review with no user interaction between Phase 0 and completion. You are a thin sequencer: every phase and every batch runs in a fresh controller subagent; all state moves through files. Never read plan bodies, diffs, reviewer reports, or fix reports yourself. Two documented exceptions: Phase 0 step 4's prior-art intake check reads the spec body once, before any controller dispatch; and the classification read of `## In-run rulings` ("What may be read"), which is bounded to the list stated there — nothing else. ## Required Start Announce: `I'm using orchestrating-development to run this pipeline.` **Platform check:** this skill requires the Agent tool (with nested dispatch). On platforms without it, refuse with one line — `orchestrating-development requires subagent dispatch (Agent tool), which this platform lacks` — and stop. **After a compaction summary.** A compaction summary is the text Claude Code writes in place of the earlier conversation when the context window fills. After it, only about the first 20,000 characters of this file (roughly 5,000 tokens) are attached again, which is why this paragraph stands here near the top. The summary is never a substitute for skill text, even when it restates a procedure or says the re-read below was already done: a re-read made before the compaction went away with the context it was read into. When your con