oversee

/oversee — human-gated, single-issue delivery for codegraph

/oversee takes one GitHub issue from "nobody has planned this" to "a verified, reviewer-clean PR waiting for a human merge", with exactly one human decision in the middle: does this plan get built? Everything else — planning, adversarial plan review, reviewer sweeps, the build, independent verification, review convergence — runs automatically.

It is the human-in-the-loop counterpart to /fixer. The two are complementary, not interchangeable:

	/fixer	/oversee
Scope	the whole qualifying backlog, in batches	exactly one issue
Plan	none — solve directly	a committed plan doc, reviewed and human-approved before any code
Human decision	none until the final report	one: tick the approval box
Merge	merges each PR itself	never merges — the human does

Use /oversee for work where getting the approach wrong is expensive: anything touching the dual-engine boundary, resolution semantics, the language registry, a public API, or an architectural decision. Use /fixer for a backlog of self-contained fixes.

You are split in two:

• You (this skill) are the gating brain. You preflight the session config, route the run, run a readiness check, drive the human approval gate, verify its provenance, validate plan freshness, and reconcile the reviewer after execution. You never write product code.
• oversee-dispatch is the execution engine. You hand it one task plus a phase, and it runs that half of the pipeline.

/oversee #<issue>    ─preflight─▶ sync main ─▶ readiness ─▶ PLAN ─▶ critic (advisory, revise-in-place)
                                                                 ─▶ plan-sweep ─▶ [Plan] PR + ✋ approval box ─▶ STOP
                                                                                   │  (a human ticks the box)
/oversee #<plan-PR>  ─preflight─▶ sync main ─▶ box ticked? ─▶ provenance? ─▶ freshness gate (Sonnet subagent)
                                                                 ├─FRESH──▶ EXECUTE (pinned to approved SHA) ─▶ VERIFY ─▶ execute-sweep ─▶ reconcile ─▶ STOP (human merges)
                                                                 ├─NARROW─▶ patch the plan in place ─▶ re-stamp the gate ─▶ STOP (needs a fresh tick)
                                                                 └─STALE──▶ carry-forward ─▶ close the [Plan] PR ─▶ re-PLAN ─▶ STOP (needs a fresh tick)

Two things make this worth running instead of just asking an agent to fix an issue:

1. A preflight config gate runs before any compute is spent.
2. The human is the plan gate, and the gate cannot be forged. The critic is advisory — its verdict is printed next to the checkbox, it never auto-advances. EXECUTE runs only after a human ticks the box, and only when a commit status the PR body's author cannot write proves the gate was installed by an /oversee run for that exact plan head.

---