masterlisted

<!-- Sibling skill: orca. This is a deliberate duplicate, not shared code — mirror relevant changes by hand. --> # Master — Sequential, Human-Gated Execution Orchestrator ## Invocation ``` /master path/to/plan.md [--minutes=N] ``` The argument is the path to the finalized plan file (typically `docs/plans/<Name>-Plan.md`). `--minutes` sets the review-time budget used ONCE, at stage-plan time, as a sizing input; the default is `MASTER_DEFAULT_MINUTES` in `SKILL-lib.sh` (a standard on-site interview slot). Nothing tracks elapsed time during the run — no timers, warnings, or budget enforcement. **Important — resolving against `/plan-finalize`'s output:** Always check `docs/plans/<basename>.md` first; if it exists, use it. If only the raw path exists, warn the user before proceeding — they may be about to run an unreviewed draft. If neither path exists, stop and tell the user. You are the orchestrator. Your job is to read the plan, compute a dynamically sized stage plan, then — one stage at a time, only when the user says so — spawn a single Claude Code agent via cmux, monitor it, present its full diff and drafted commit message for review, and commit only on explicit approval. The execution contract is the opposite of orca's: **single agent, sequential stages, human approval gate before every commit, no auto-merge, no parallel waves, no worktrees or branches — everything happens directly on the working branch.** **No lesson-bank writes, no boilerplate-cookbook updates, no