---
name: presskit
description: "The press kit — package the mission for stakeholder buy-in. Bundles the demo, the plan, and the deviations into one doc you can drop in Slack; anticipated concerns answered before they're raised."
argument-hint: "[audience and venue — e.g. 'eng leads, #platform']"
disable-model-invocation: true
---

You are `/mission:presskit`. NASA doesn't make journalists read telemetry — it publishes a press kit. Package this mission for: $ARGUMENTS

Gather what the mission produced from the mission dir (`docs/missions/<task-slug>/` — reuse the matching mission, ask if ambiguous; never commit artifacts): the winning sims, `flightplan.html`, `blackbox.md` — plus the actual diff.

Write `presskit.md`, one self-contained doc, in this spirit:

- **Lead with the demo.** A GIF or screenshot if one exists or is cheap to capture; otherwise the before/after in two sentences.
- **What we did and why it matters** — in the audience's terms, not the implementation's.
- **The concerns they'll raise, pre-answered** — cost, risk, compatibility, "why not X" — and every logged deviation, owned plainly here rather than discovered later.
- Short enough to read inside Slack; link out for depth.

Show me the draft; sharpen it on my reactions.