APromptAura
0

Weekly challenge: turn meeting notes into action items nobody argues about

auto-checked, 2 hours old
AauraNovice

The prompt

0 copies
This is the first PromptAura weekly challenge. Post your entry as a prompt in p/productivity, tag it `weekly-challenge`, and include an example output. THE BRIEF Write a prompt that takes raw, messy meeting notes and produces a list of action items that survives contact with the people who were in the room. That means: - Every item has exactly one owner, named - Every item has a date or an explicit "no date agreed" - Anything that was discussed but not decided is listed separately as open, not silently promoted into a task - Nothing is invented. If the notes do not say who owns something, the prompt must say so rather than guessing Test it on your own real notes, not on a clean sample. The whole point is handling the mess. HOW ENTRIES ARE JUDGED Verified runs decide it, not upvotes. Whoever's entry collects the most "worked for me" verifications by the end of the week wins. That means you should run other people's entries and report honestly, including when they fail. WINNER GETS A pinned spot on the p/meta feed for the following week, and the founder flair on their profile. THE PROMPT BELOW IS THE BASELINE TO BEAT You are turning raw meeting notes into action items. Notes: meeting_notes Rules: - One owner per item, named exactly as they appear in the notes - If no owner is identifiable, put the item under Unassigned and do not guess - If no date was agreed, write "no date agreed" rather than inventing one - Anything discussed without a decision goes under Open questions, never under Actions - Do not add items that are not supported by the notes Output format: Actions - [owner] [action] [date or "no date agreed"] Unassigned - [action] Open questions - [question]

Run it in your model, then come back and report whether it worked, including the model and version.

Where it has been run

People and our automated sweep are counted separately. Only the People column is someone vouching for this prompt.

ModelVersionPeopleBrokeAutoLast
ClaudeHaiku 4.5001/12 hours ago

Example output

Actions - Priya: send the revised pricing deck to Marcus, Friday - Marcus: confirm whether the enterprise tier includes SSO, no date agreed - Dana: book the follow-up with the design team, next Tuesday Unassigned - Update the onboarding docs to match the new tier names Open questions - Do we grandfather existing customers onto the old pricing, or migrate them at renewal? Discussed for ten minutes, no decision reached. - Whether SSO is a tier feature or an add-on. Priya and Marcus disagreed.

0 comments

Sign in to comment or report what this prompt did for you.

Sign in

No comments yet. Run the prompt and report what you got.