Process Meeting Notes
The scenario
You just got out of a 45-minute sprint planning meeting. Decisions were made, action items were assigned, but your notes are a mess — half-sentences, abbreviations, things you'll forget by Monday. Instead of spending 30 minutes cleaning them up (or never doing it), you'll paste them in and get structured notes in 2 minutes.
Example output
Meeting Notes: Sprint 14 Planning
Date: Jan 30, 2026 · Attendees: Sarah, Mike, Priya, Jordan
Decisions Made
- Ship nav redesign to 50% of users by Feb 3 (was 25%)
- Defer dark mode to Sprint 16 — blocked by design resources
- Approved $5k budget for external usability testing vendor
Action Items
Owner Task Due Mike Expand nav rollout config to 50% Feb 3 Priya Get 3 vendor quotes for usability testing Feb 5 Sarah Update roadmap to reflect dark mode delay Feb 1 Jordan Draft customer comms for dark mode delay Feb 3 Key Discussion Points
- Nav redesign metrics are strong: 34% reduction in navigation taps
- Dark mode delay is a bandwidth issue, not a technical one
- CEO wants usability testing before full nav rollout
Open Questions
- Do we need legal review for the new usability testing vendor?
- Should we proactively communicate the dark mode delay to customers?
Suggested Next Meeting Agenda
- Review 50% nav rollout metrics
- Usability testing vendor selection
- Q2 roadmap draft review
How to create this in 5 minutes
Step 1. Make sure your Product Management OS folder (second-pm-os) is open in Claude.
Step 2. In the chat panel, type:
/meeting-notes-processor
Step 3. Paste your notes. Any format works — bullet points, stream of consciousness, even a raw transcript from a recording tool. The messier, the more time you save.
Here's an example of what you might paste:
sprint 14 planning - sarah mike priya jordan
talked about nav redesign - metrics look good, 34% less taps
want to expand rollout to 50% by feb 3, mike handling
dark mode pushed to sprint 16, priya's team doesn't have bandwidth
not a tech issue just resources
approved 5k for usability testing, priya getting quotes
jordan needs to write something for customers about dark mode delay
ceo wants usability testing before we go to 100% on nav
sarah updating roadmap
need to check if legal needs to review the testing vendor
Step 4. Claude extracts decisions, action items, and discussion points, then saves structured notes to:
stakeholder-updates/outputs/meeting-notes-processor-[topic].md
If something doesn't look right
Tell Claude what to change. For example:
- "You missed an action item — I also need to send the nav metrics to the CEO by Monday"
- "Add Priya's quote about why dark mode is delayed"
- "The due date for vendor quotes should be Feb 7, not Feb 5"
- "Make the summary shorter — just decisions and action items"
What's next?
- Write a Status Update — Turn this week's progress into an executive update
- Get Stakeholder Feedback — Simulate feedback on a document before sharing it