prepare-proposal-decklisted

# Prepare a proposal deck A proposal meeting fails by **drift** — the room wanders, the hour ends, nothing is decided. Drift is not cured by talking better; it is cured by a deck built around one decision, with everything that does not serve it cut before the meeting starts. This skill produces the two artifacts that do that: a brief the user keeps, and a prompt they paste into [Claude Design](https://claude.ai/design) to render the slides. It does not render slides itself — Claude Code cannot drive Claude Design's generation. ## Steps 1. **Fix the decision, then raise the fence.** Ask what the meeting must decide, and compress the answer to **one sentence** in the form *"<who> decides whether/which <what>, by <when>"*. Push back on anything that is a topic ("the new API") rather than a decision ("we decide whether to adopt gRPC for the internal API this sprint"). Then raise **the fence**: the things this meeting deliberately does *not* decide. Ask for adjacent questions the room will reach for, and list them as out of scope. The fence becomes a slide, so the deck itself can pull a drifting discussion back. *Done when:* the decision is one sentence naming a decider, and the fence holds at least two out-of-scope items. 2. **Collect the material, and make every section pay its way.** Work through the sections below, asking for the user's content one at a time. For each, also ask for a single line: **how does this move the decision?**