goal-supervisor

You are operating the goal-supervisor skill — the mission-level layer sitting one above individual goals. Where the judge gates a goal against its DoD, the supervisor gates the mission against its charter and decides what goal to run next.

The gk CLI (python3 "${CLAUDE_PLUGIN_ROOT}/scripts/gk.py", abbreviated gk) owns all mission mechanics: initialization, brief assembly, verdict application, and every write to mission.json / mission-log.md / mission-completed.md (a PreToolUse hook blocks direct edits to those while the mission is live; the user's charter mission.md is never blocked). Your job: spawn the supervisor subagent and relay its verdict faithfully.

Mental model

Mission                                         ← .claude/mission.md (user-authored charter)
  ├─ Goal A   (done, in _archive)               ← goalkeeper contract — within-goal loop works
  ├─ Goal B   (done, in _archive)               ← drafted in response to A's output
  └─ Goal …   (drafted on demand by supervisor) ← what /goal-supervisor produces

The supervisor is NOT a chain. Chains commit to a linear sequence at chain-start. The supervisor decides direction adaptively based on what the prior goal actually produced.

When to invoke

• After a standalone goal completes (gk status reports "No active goal").
• When a multi-goal mission is in flight and you want the next goal to be informed by the prior one.
• NEVER while a goal is in flight — gk refuses (active, paused, and needs_human all count as in-flight).

Mission charter (mission.md) — expected shape

The charter is user-authored — the skill never auto-drafts missions. Sections (none syntactically required, all strongly recommended):

# Mission: <name>

## Objective

<one-paragraph statement of the mission's high-level intent>

## Success condition

<concrete, observable condition for "mission done." Like a goal's definition_of_done
but at the mission level. Specific. Measurable.>

## Constraints

<bulleted list of hard rules. The supervisor will refuse to propose goals
that violate these.>

## Legal next-goal shapes

<bulleted catalog of the kinds of goals this mission may need. The supervisor
draws from this list when proposing next-objectives. Each entry: name +
1-sentence description.>

## Done is not

<bulleted list of things that look like progress but don't satisfy the
success condition — equivalent to a contract's non_goals at the mission level.>