execution

Execution

What this is

The canonical front door for turning a reviewed, double-SHIP'd plan into code. There is exactly one execution skill; both ways of running a plan — with you in the loop, or unattended — live here behind a single driver choice. This skill is intentionally thin: it picks the driver, normalizes the plan's split directive, and hands off to the existing flow that does the real work.

For the one-page mental model of the three independent choices (driver, split, review), see the canonical docs/execution-model.md. This skill is the selection layer over the engines described there; do not restate the matrix here.

Inputs

driver: interactive | autopilot
plan:   docs/plans/<plan>.md | omitted-for-resume

• driver: interactive — run the plan step-by-step with the user in the loop, pausing for review.
• driver: autopilot — run the plan unattended end-to-end, persisting progress to the sidecar.
• plan — the path to a reviewed plan. May be omitted only for autopilot resume (see selection rules).

Selection rules

1. Invoked by /autopilot. The command supplies driver: autopilot and forwards its arguments unchanged. This is the thin-alias path — behavior is identical to running /execute with driver: autopilot.
2. Invoked by /execute with a plan path. Require an explicit driver of either interactive or autopilot. If driver is missing, apply rule 5.
3. Invoked by /execute with no arguments. Resume is autopilot-only in v1: scan the sidecars exactly like a no-argument /autopilot does, resume only if exactly one autopilot run is in progress, and otherwise show the same "no run / several runs" choice or error that /autopilot shows. No-argument invocation never starts or resumes an interactive run.
4. driver: interactive is not resumable in v1. It must be invoked with a plan path. If a session ends mid-work, the user restarts interactive execution by pointing at the plan again and choosing the next unfinished work item. This skill must not infer an interactive run from sidecar state, because no interactive active-run contract exists today.
5. Invoked directly as a skill with a plan path but no driver. Ask exactly one short question: "Run this step-by-step with you in the loop, or let autopilot continue the reviewed plan?" Then proceed with the chosen driver.
6. driver: interactive delegates to the existing interactive driver flow after split normalization (see ## Driver: interactive).
7. driver: autopilot delegates to the existing autopilot flow after split normalization (see ## Driver: autopilot).
8. Stale-run surfacing (v0.15.0). On every entry, run node "${CLAUDE_PLUGIN_ROOT}/lib/codex-bridge/cli.js" sidecar-scan-stale --repoRoot <repo> and, if it returns any entries, tell the user in plain English before proceeding: which plan, which step it stopped at, and how long it has been idle (e.g. "an unattended run for stopped at slice 4 planning 11 days ago — resume it, or mark it halted?"). A quiet in-flight run is otherwise indistinguishable from one running in another session, and replay found one sitting silently resumable for 11 days.

What this delegates to

• driver: interactive → codex-paired-superpowers:subagent-driven-development (the step-by-step, user-in-the-loop flow).
• driver: autopilot → codex-paired-superpowers:autopilot (the unattended, self-continuing flow).

Both flows already normalize the plan's split directive before dispatching work; this skill simply routes to the right one based on driver.

User-visible output

Write status updates in plain English. Do not leak internal labels — words like slice, SHIP, or Phase B — into anything the user sees. Describe what is happening in terms the user recognizes: "working through the first piece of the plan", "ready for your review", "all done". Internal artifacts (commit messages, sidecar records, test names) may use the precise terms; user-facing prose may not.

Driver: interactive

Run the plan step-by-step with the user in the loop. The implementation flow lives in codex-paired-superpowers:subagent-driven-development; this driver reaches it through execution so the user-facing entry point stays execution.

For each work item in the plan:

1. Normalize the split directive for the work item and route it through runSplit (the same normalize-then-route seam autopilot uses). runSplit resolves the work item to one of three split paths: single, two-disjoint, or hybrid-ui-backend.
2. Run the corresponding split path (see below).
3. Run the domain reviewers for the work item using the reviewer-named APIs.
4. Run the Codex paired review for the work item.
5. Show plain-English progress and blockers to the user, pausing for review between steps.

Split-specific behavior (interactive uses the same split it would under autopilot):

• single → runSplit returns a dispatch-single directive. Act on it by running the existing Step A implementing-subagent dispatch from subagent-driven-development (one implementing subagent / foreground implementer), then the reviewer checks and Codex review.
• two-disjoint → use the existing implementer worktree fan-out and dispatchImplementers, then the existing merge coordinator and post-merge review. The interactive driver may pause between dispatch, merge, and review, but it is the same split reachable under autopilot.
• hybrid-ui-backend → call runHybridSlice({ mode: 'interactive', ... }). The UI owner runs as claude-inline; the backend owner runs as codex-background-bash. This reuses the runner behavior already in lib/codex-bridge/hybrid/runner.js — no new runner.

Dirty working tree before a hybrid step. runHybridSlice in interactive mode refuses to start if the working tree has uncommitted changes (internal halt hybrid-preflight-dirty). Do not show that code to the user. Instead say, in plain English: "Your working tree has uncommitted changes; commit or stash them before running a hybrid step, then re-run." Then stop and wait for the user.

Interactive execution has no no-argument resume in v1 and always requires a plan path (see selection rules 3-4).

Driver: autopilot

Delegate to the codex-paired-superpowers:autopilot skill unchanged. The only thing this driver adds is reading the canonical **Split:** directive at autopilot's existing Phase B decision point — the point where Phase B already chooses among single, implementer-experts, and hybrid — via normalizeSplit.

• For a single work item, the router returns the dispatch-single directive (the Plan 1 split router), and autopilot runs its existing single-implementer phase on that directive. Autopilot — not the router — still owns that dispatch. Do not bypass the router and call the single-implementer phase directly; always go through dispatch-single so the split decision stays in one place.
• For two-disjoint, autopilot's existing implementer-experts branch runs (dispatchImplementers).
• For hybrid-ui-backend, autopilot's existing hybrid branch runs (runHybridSlice({ mode: 'autopilot', ... })).

Everything else stays owned by autopilot: resume discovery, sidecar state, the halt envelope, outer-mode behavior, and self-continuation across sessions. This driver introduces no new resume path, no new flags, and no new prompts.