Turn a decision you're sitting on into an async proposal
Decisions that live in someone's head or in a Slack thread never get made cleanly. This prompt structures a decision into a document that stakeholders can review and respond to without a meeting.
You are my chief of staff helping me write a clear async decision proposal. Here is the decision I need to make: {{DECISION_TO_MAKE}}. Here are the options I am considering: {{OPTIONS}}. Here is relevant background or data: {{BACKGROUND_AND_DATA}}. Here are the stakeholders who need to weigh in: {{STAKEHOLDERS}}. Here is my deadline for making this decision: {{DECISION_DEADLINE}}.
1. Write a one-sentence problem statement that is specific enough that any reader understands what is actually being decided.
2. For each option, write: (a) a plain description of what this option entails, (b) the strongest argument for it, (c) the strongest argument against it, and (d) what would have to be true for this to be the right choice.
3. State my current recommendation and the primary reason for it. If I haven't provided a recommendation, ask me before proceeding.
4. Write a clear ask for each stakeholder: what specifically do I need from them, and by when? Do not use 'thoughts?' as the ask.
5. Add a brief section on what happens if the decision is not made by the deadline — this makes the cost of inaction visible.
6. Format the document so it can be pasted into Notion or an email and read in under three minutes.
If the options I listed are not genuinely distinct — if one is clearly a subset of another — flag that before writing. {{DECISION_TO_MAKE}}{{OPTIONS}}{{BACKGROUND_AND_DATA}}{{STAKEHOLDERS}}{{DECISION_DEADLINE}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{DECISION_TO_MAKE}}{{OPTIONS}}{{BACKGROUND_AND_DATA}}{{STAKEHOLDERS}}{{DECISION_DEADLINE}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Grammarly
$12/moGrammar, tone, and clarity across every app.
Grammarly remains the default for grammar + tone checking. The 'Grammarly Go' generative features are catching up but are not the main reason to subscribe.
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.