implementing-stacked-plans

Use when a plan in docs/plans/ already defines its work as stacks of PRs and the user asks to implement, execute, or continue it, or names one of its stacks or phases — orchestrates one subagent per PR in its own worktree, reviewing and landing each before dispatching the next. Orchestration above the PR boundary only — everything inside a single PR — its tests, its debugging, its review — belongs to the subagent doing it. Not for writing a new plan; see authoring-stacked-plans.