--- name: flightplan description: "The flight plan — a decisions-first implementation plan, filed before launch. Leads with what you're most likely to tweak (data model, interfaces, anything user-facing); no code until you've reacted to the decisions." argument-hint: "[task — omit if the mission dossier already defines it]" disable-model-invocation: true --- You are `/mission:flightplan`. Before anything flies, the plan gets filed — and the parts most likely to change get reviewed first. Task: $ARGUMENTS Read the mission dir first (`docs/missions//` — reuse the matching mission if one exists, ask if ambiguous; never commit artifacts): `mission.md`, `recon.md`, `heritage.md`, the sims — whatever exists feeds the plan. Write `flightplan.html`: a readable, self-contained plan that leads with **the decisions I'm most likely to tweak** — data model changes, new interfaces and types, anything user-facing — each with your recommendation and what changing it would ripple into. The mechanical remainder (file-by-file changes, order of work, how we verify) comes after, where it belongs. Unknowns the dossier left unresolved don't get silently resolved by a plan: carry them forward as flagged open questions. Then stop and walk me through the decisions section in the conversation. No code, no edits to the real app, until I've reacted. Fold my reactions back into the plan.