# /supervise Skill

**Purpose:** Run a session as a supervisor over MiniMax subagents. A 15-min cron tick reaps finished `mm-worktree-task` units, files new bugs, and dispatches a unit per in-focus work item; a 30-min cron report gives bugs worked/resolved and feature progress. Replaces two hand-pasted loop prompts.

**Location:** `custom-claude-skills/skills/supervise/SKILL.md`.

## Usage

`/supervise [focus text]` (bare = pick focus from the planner via AskUserQuestion), then `/supervise focus|push on|off|status|stop`. `tick` and `report` are what the crons fire.

Requires: planner-backed project (`cp-cli planner`), `mm-worktree-task`, MiniMax profile.

## How it works

- Cron prompts are just `/supervise tick` / `/supervise report`; all logic and memory live in the skill and `.supervisor/state.md` (focus, ledger, in-flight units, cron ids).
- On start it creates `.supervisor/`, adds it to `.gitignore`, and appends a marked `<!-- supervisor:begin -->` section to the project CLAUDE.md (left uncommitted) so other sessions know a supervisor owns those worktrees.
- Report counts come from the ledger, with "resolved" verified against the planner.
- Merged work stays local unless `push: on` (pushes may trigger deploys).

## Gotchas

- Crons are session-only and auto-expire after 7 days; after a restart `/supervise` resumes from state and recreates them.
- One unit per item (no cap on items) — a bare "dispatch if none underway" duplicates units; the in-flight table prevents it. Items with overlapping files are queued, not parallelised.
- Always re-run the suite after a unit's last commit; units' own green claims are not trusted.