mission-initlisted

Bootstrap an orchestrated mission: create a dated folder under docs/missions/ with GOAL.md, features.json, PROGRESS.md, and the first WORKER_TASK from the repo's templates. MUST be used whenever the user says "start a mission", "new goal", "bootstrap the loop", "let's run the orchestration on X", or asks to begin orchestrated work of any kind. Also use to re-scope an existing mission. Produces files mechanically from docs/missions/templates/ — never freestyle the formats. Runs fleet-inventory at GATE 0 and always shows the seat→model map for human confirm/swap. Default chair is Opus (Cursor intake plans briefly; Opus weighs and orchestrates) unless the human names otherwise.
hashorva/purrfect-harness · ★ 0 · Data & Documents · score 60

Install: claude install-skill hashorva/purrfect-harness

# Mission init (orchestrator only) ## Step 0 — Preconditions - No active mission: run `bash scripts/active-mission.sh`. If it prints a path, STOP and ask the human whether to finish (`status: done`), keep waiting on a gate, or re-scope. Never start a second `in-progress` / `awaiting-gate` mission. - Also refuse leftover root `GOAL.md` / `features.json` (pre-2.0 layout) — move or delete them first. - Read AGENTS.md (hard rules constrain every feature) and skim docs/ filenames so features reference real docs. - Load `docs/missions/MODEL_ROUTING.md` once for this GATE 0 decision. ## Chair resolution (before writing files) Default brain = **Opus**. Exceptions (human must say, or session already is): | Signal | Chair | |---|---| | Already on Opus (Claude Code **or** Cursor UI) | This session | | “You are the orchestrator” / “no handoff” | Current model | | “No orchestration — just execute” | STOP mission-init; implement in chat | | “Orchestrator = Fable” | Fable (**named only** — never auto-escalate) | | “Orchestrator = Codex highest” / Sol | Inventory `brain_codex` / family `sol` | **Cursor intake:** if a brief plan exists in a Cursor (often Grok) chat, Opus reads it, weighs whether the split looks balanced, then continues mission-init. Do not treat the intake chat as the orchestrator unless named above. ## Step 0b — Local CLI inventory (mandatory) ```bash command -v claude; command -v codex; command -v agent; command -v agy bash scripts/fleet-inventory.sh ``` Al