Mission Plan — Markdown + Knowledge Graph

Emits the second of the three Voltron mission documents: what each Lion will do, what the mission cannot yet do, and what could go wrong.

Read the format reference first: ${CLAUDE_PLUGIN_ROOT}/kb/mission-knowledge-format.md. It defines the JSON-LD envelope, the URN identifier scheme, the schema.org type mapping, the actionStatus vocabulary, and the pre-write validation steps.

What a plan contains

Procedure

1. Reuse the mission slug from the existing mission-brief. Read the brief's .jsonld to recover urn:voltron:mission:{slug} rather than re-deriving it from the objective — re-deriving drifts, and a drifted slug silently forks the mission into two graphs.
2. Draft assignments. One Action per Lion task. Enforce the file-ownership rule: no two assignments may list the same file in object. This is checkable in the graph, so check it — group every assignment's object @ids and confirm no path appears twice.
3. Run Skills Gap via the skills-registry skill and its actions-map.json. Status is covered, use-existing-skill:{name}, or needs-new-skill. A registry entry marked conditional counts as covered only when its requires precondition is actually met — otherwise record the unmet precondition in Notes.
4. Build the Risk Register. Categories: technical, scope, integration, data-loss. Severity is L, M, or H. Every risk gets a mitigation, even if that mitigation is "accept and monitor".
5. Write mission-plan.md as three tables, then mission-plan.jsonld. At plan stage every assignment carries PotentialActionStatus — the plan describes intent, not outcome, and nothing is Completed before the Lions have run.
6. Update the mission node so member lists every Lion that now has an assignment, and subjectOf includes the plan.
7. Validate per the KB checklist, then report both paths.

Writing rules

• Each assignment's Acceptance must be observable by someone who did not write the code.
• If a Lion has no work this mission, omit them. Do not pad the table to five rows.
• Depends On names another assignment's @id, not a prose description — that is what makes the dispatch order derivable from the graph instead of from reading the table.
• Files in object are repo-relative paths, matching urn:voltron:file:{path} exactly.

The go/no-go gate

The plan is the document the user approves. After writing it, present the three tables and stop:

"Mission ready. Reply go to dispatch Lions, no-go to revise, or edit <section>."

Do not dispatch Red, Blue, or Yellow Lion before that approval, and do not write mission-report until the Lions have actually reported.