run-planlisted

# Implementing a plan Run a plan task by task through delegated contexts, so the session that commits stays small. The enemy is reading the whole plan or building in the session: both spend the context the review and the pull request need. The overcorrection is delegating a decision: a task with a `Design:` line needs a judgment only the session can make. Invoking `/exo:run-plan` on a plan authorizes the workspace you pick at step 1, a wave's temporary worktrees beside it, commits there as steps 6 and 7 time them, and the review's fixes; a push or a pull request only after your answer to the finish question, and nothing else. ## When to use - A `define-scope` brief with a `## Tasks` list, or an older plan, to run or resume, named or found for the current branch. - Not for writing or repairing the task list (`define-scope`), a change without a plan (`build-change`), or a failure whose cause is unproven (`find-cause`). ## The loop 1. **Resolve the plan, then the workspace.** Use the path the user named; without one, take the plan under `docs/plans/`, `docs/specs/` or `~/.claude/plans/` whose `Repository:` line equals `git rev-parse --show-toplevel`, prefer one whose `Branch:` equals the current branch, and name the pick. Then settle where the run commits as `references/workspace.md` says, before any dispatch; it covers the plan's `Branch:` and a `Repository:` folder not yet under git. Then write four lines to `exo/run-plan.active` under the session directory's `git rev-pa