Pre-Read That Gets the Decision

When to use it

The user has a meeting coming where a group must decide something, and past meetings on the topic have ended in more discussion. They want a pre-read that makes the meeting a decision point. Notes, options and the attendee list in; one short pre-read out, with the meeting's first five minutes scripted.

Not for a decision one person can make by email (use One-Page Decision Memo) and not for the notes and actions after the meeting (the Meeting Notes and Actions pack does that).

What it asks you

One message, numbered.

1. The decision the meeting must make, in your words.
2. The meeting: date, length in minutes, and who is attending with their role. Who is the final decider if the room splits?
3. The options on the table. If there is only one, say so.
4. The facts you have: numbers, dates, constraints, what has already been tried. Paste raw.
5. Your recommendation, if you are allowed to have one in this room. Some chairs must stay neutral; say which you are.
6. What has stopped this decision before. A missing person, a missing number, a disagreement nobody names.

If the user does not know the slot length, assume nothing: ask once, and if no answer, write the pre-read to a 5-minute read and say so. If the user cannot say what has stopped the decision before, the pre-read still works, but the "what we need from you" lines will be weaker, and the output says so. Never invent an attendee's view, a number or a prior decision.

What comes back

Plain text.

PRE-READ: meeting title, date, length. Reading time: N minutes. DECISION: the question DECIDER: name or role NEEDED BY: date Read this, then reply before the meeting with one word: agree, disagree, or a question.

OPTIONS A. Name What: ... Cost: ... Time: ... Main risk: ... Who does the work: ...

B. Name (same five lines)

RECOMMENDATION (only if the user may give one): option letter, one line

WHAT WE NEED FROM YOU - Name or role: the one thing to bring

FIRST FIVE MINUTES (for the chair) 1. Read the decision question aloud. 2. Ask who has read the pre-read. 3. State who decides if we split. 4. Ask the person most likely to disagree to speak first.

AFTER THE MEETING: who writes the decision down and by when; the next step under each option

BACKGROUND (three lines at most)

(N words of body) Next: one line naming the single most useful next step.

• 00_START_HERE.pdf: the two-minute set-up for each AI.
• 1 - Skill: pre-read-that-gets-the-decision.zip, one upload to Claude, ChatGPT, Gemini, Grok or Microsoft 365 Copilot. It switches on by itself when this job comes up.
• 2 - Text file for any AI: the same Move as one .txt. Attach it to any chat, on any plan, and type "Follow this file".

It drafts, you read and send. It never contacts anyone for you and never invents a fact, a number or proof.

A Move is a single play. The whole function in a box is Meeting Notes to Actions, an agent pack with up to 8 skills.