Supervise Plan

Continuity daemon for a multi-session execute-plan run. The orchestrator does the work and decides when to pause — it logs PAUSED at a wave boundary when its context runs high (its Step 1.10). This skill owns only continuity — respawn and notify — and stays deliberately ignorant of the plan's content. Fresh orchestrator sessions start with zero conversational state because execute-plan resumes from disk (checkboxes + Base SHA).

Protocol

Input

• Spec folder: meta/specs/NNN-slug/ containing plan.md. Run this skill from the project repo containing the spec folder — the self-gauge and launcher assume that working directory.
• Optional override: Ghostty font size (default 17).

Step 0 — Bootstrap

1. Verify plan.md exists and its Status is not FROZEN — otherwise tell the user and stop.
2. If the mailbox doesn't exist: create it (format in Mailbox format) and append supervisor | initialize execute-plan | total N waves | HH:MM — N = the count of ### Wave headings in plan.md, the one look at plan structure this skill takes. The mailbox's existence is what switches on execute-plan's wave-boundary checkpoint.
3. If the mailbox has no orchestrator | line, spawn the orchestrator via the Launcher with command claude "/execute-plan meta/specs/NNN-slug".
4. Invoke the loop skill via the Skill tool with the watch cycle (Step 1) as the recurring prompt, every 10 minutes.

Step 1 — Watch cycle (each wake)