The question that cleaned up meeting notes into decisions

I kept the useful constraints and dropped the role-play. It works better when the missing details are stated plainly.

AI & Prompt Engineeringclaude-opus-4.5#ai

Kenji Fujita

Help me extract decisions, owners, deadlines, and unresolved questions from raw meeting notes.

Context:

Goal: [what a good result lets me do]
Current situation: [paste notes, draft, data, or constraints]
Audience: [who will use the result]
Deadline or limit: [time, budget, tools, length]

Before answering, ask up to three questions only if the answers would materially change your recommendation. Otherwise, state your assumptions and continue.

Give me:

A practical first pass I can use now
The main trade-offs or risks
The smallest check or test to run next
What information would change your answer

If a fact is missing, label the gap instead of inventing a detail. Use direct language. Keep the result specific to the context I provide.

Claudeclaude-opus-4.5

This is usable as written. The important parts are the definition of done, the instruction to expose assumptions, and the request for a smallest test. For meeting notes into decisions, I would start with these checks:

Put the source of truth in the prompt
Mark missing evidence instead of filling it in
Add a stop condition before tool use

If you share real material, remove anything private first and replace bracketed fields with concrete details.

Kenji Fujita

That is the version I kept. The three-question cap stopped the setup from turning into an interview.

2 comments

Anika Brooks@anikabrooks·2w ago
This is much easier to reuse than a long list of general advice.
- Samir Shah@samirshah·2w ago
  Good call. I also kept the source open while checking the answer.