mission

Plugin mission from marketplace codercoco-custom-plugin-marketplace in CoderCoco/claude-plugin-marketplace. Commands read from the repo's manifest — 14 days ago.

Skills (8)

• comms

  Use when the mission PR has review comments to address. Runs a single-pass fetch→triage→fix→reply cycle and saves state. For continuous watching, guide the user to run `/loop 5m /comms <PR>`. Trigger on "comms <PR>", "/comms", or when the user wants to handle PR review comments.

• docking

  Use when the mission branch is ready for a pull request, or when /mission dispatches the PR phase. Trigger on "docking <N>" or "/docking". Thin wrapper around docking-workflow.js — pushes the branch, opens a PR with Closes #N, moves the project board card, then offers a comms watcher. Requires a pla

• liftoff

  Use when the user wants to build the planned tasks for a mission issue, or when /mission dispatches the build phase. Trigger on "liftoff <N>" or "/liftoff". Thin wrapper around liftoff-workflow.js — Astronauts implement tasks in dependency rounds, Flight Controllers verify, commits land in the workt

• mission-debrief

  Use when the user wants to add new code-review findings to the Systems Inspector's rubric, has review feedback to record, pastes a postmortem of issues a reviewer caught, or mentions "mission debrief", "add to rubric", "the Systems Inspector missed these", "update the review checklist". Takes free-f

• mission

  Use when the user wants to start or advance the full end-to-end mission workflow for a GitHub issue. Trigger on "/mission <N>", "mission issue N", "continue mission", "/mission --status", or any signal that the user wants to orchestrate an issue through plan→build→review→PR. Top-level orchestrator —

• pre-launch

  Use when the user wants to plan a GitHub issue in the mission workflow, or when /mission dispatches planning. Trigger on "pre-launch <N>", "/pre-launch", or "replan issue N". Dispatches the Flight Director (branch and worktree are created during planning), which resolves ordinary ambiguity autonomou

• setup

  Use when the user wants to configure which models the mission crew uses. Trigger on "mission setup", "configure mission models", "mission config", or "/setup" in a mission context. Interactive walkthrough that writes .claude/mission.local.md with per-role model defaults consumed by all mission skill

• systems-check

  Use when the user wants the mission code review phase, or when /mission dispatches it. Trigger on "systems-check <N>" or "/systems-check". Thin wrapper around systems-check-workflow.js — language-bucketed Systems Inspectors review the full branch diff, repair Astronauts fix actionable findings; on e

Subagents (5)

• astronaut

  Use as an Astronaut in the mission crew. Implements exactly ONE task from a Flight Director's plan — no more, no less. Edits the files named in the task, follows the acceptance criterion, and reports back. Invoke once per plan task. Also invoke to re-implement a task when the Flight Controller has r

• capcom

  Use as CAPCOM in the mission crew. Categorises incoming PR comments so Mission Control knows which to act on, which to answer, and which to ignore. Invoke once per comms round with the new comments since the last visit.

• flight-controller

  Use as the Flight Controller in the mission crew. Reviews an Astronaut's just-completed task — reads the diff, runs tests/lint/build, and emits a PASS or FAIL verdict with concrete fixes when failing. Invoke after every Astronaut task. Also invoke as a final sweep once all plan tasks complete.

• flight-director

  Use as the Flight Director in the mission crew. Produces a DAG implementation plan for a GitHub issue — explores the repo, lists discrete tasks each small enough for one Astronaut, assigns crew names, declares file dependencies, and states acceptance criteria. Invoke when Mission Control needs a fre

• systems-inspector

  Use as the Systems Inspector in the mission crew. Reviews the diff for a specific language bucket against the living review rubric, surfacing semantic and quality issues the Flight Controller's mechanical checks cannot catch. Invoke in parallel — one Systems Inspector per language bucket — after lif