Meeting Notes to Next Actions

The Prompt

You are an operations facilitator who converts messy meeting notes into a practical execution plan.

MEETING NOTES:
{{meeting_notes}}

TEAM CONTEXT:
{{team_context}}

DECISION DEADLINE:
{{decision_deadline}}

KNOWN CONSTRAINTS:
{{known_constraints}}

Produce:
1. Key decisions already made (bullet list).
2. Open decisions still unresolved (with recommended owner for each).
3. Action plan table with: action, owner, due date, dependencies, risk if delayed.
4. 48-hour follow-up message draft to the team.
5. "What could slip" section: top 3 delivery risks and one mitigation each.

Rules:
- Prefer concrete verbs (draft, review, approve, ship) over vague items.
- If owner is missing, mark as "UNASSIGNED" and suggest likely owner role.
- Flag contradictions in notes explicitly.
- Keep output concise and execution-ready.

When to Use

Use this right after planning or cross-functional meetings where notes are long but accountability is unclear. It works best when a team needs immediate clarity on ownership, deadlines, and unresolved decisions.

Variables

Variable	Description	Example
meeting_notes	Raw notes or transcript snippets	”Roadmap sync notes copied from docs”
team_context	Team structure and responsibilities	”PM owns scope, Eng lead owns implementation sequencing”
decision_deadline	Final date for unresolved decisions	”By Friday EOD”
known_constraints	Capacity, legal, technical limits	”Two engineers available, compliance review needed”

Tips & Variations

• Ask for a “week-by-week timeline” when the work spans more than two weeks.
• Add “format as Slack update” to get an immediately sendable status message.
• For recurring meetings, ask the model to compare this week’s actions to last week’s unfinished items.

Example Output

• Decision made: API launch stays behind feature flag.
• Open decision: Pricing tier packaging, owner suggested: Product Lead.
• Action row: “Draft customer migration email” | Owner: Marketing | Due: Mar 3 | Dependency: final pricing copy.