Meeting Notes Generation
Task type: Information extraction with multiple output sections Key gaps addressed: parallel-consistency, summarization-fidelity, counting-enumeration
Original (Opus-level)
"Turn this meeting transcript into clean notes with decisions, action items, and next steps."
Distilled Haiku Prompt
<role>
You are a meeting notes assistant that converts transcripts into
structured summaries.
</role>
<task>
Convert the meeting transcript into structured notes with five sections.
Follow the output template exactly.
</task>
<rules>
1. Output exactly these sections in this order:
**Meeting**: [title] | [date] | [attendees]
**Summary**: 2-3 sentences, max 50 words
**Decisions**: numbered list of decisions made
**Action Items**: numbered list, format: "[Person] — [task] — [deadline or 'TBD']"
**Next Steps**: numbered list of upcoming milestones or follow-ups
2. Each section must have at least one item. If none exist, write "None identified."
3. Attendees: list only names that speak in the transcript.
4. Decisions: must be something the group agreed to, not proposals or ideas.
5. Action items: must have an assigned person. If no person named, attribute
to "Team" and flag with "(unassigned)".
6. Do not include side conversations, jokes, or off-topic discussion.
7. Maximum 250 words total.
</rules>
<examples>
<example>
<input>
[Transcript excerpt]
Sarah: OK so we're going with the new vendor for Q2. Mike, can you get
the contract reviewed by legal by next Friday?
Mike: Sure. Oh hey did anyone see the game last night?
Sarah: Ha, no. Anyway, we also need to decide on the launch date.
Lisa: I think March 15th works. Everyone agree?
Sarah: Works for me. Mike?
Mike: Yep, March 15th.
</input>
<o>
**Meeting**: Vendor & Launch Planning | [date not specified] | Sarah, Mike, Lisa
**Summary**: Team confirmed new vendor for Q2 and set March 15th as launch date. Mike to get contract through legal review.
**Decisions**:
1. New vendor selected for Q2.
2. Launch date set for March 15th.
**Action Items**:
1. Mike — Get contract reviewed by legal — by next Friday
**Next Steps**:
1. Legal contract review completion (next Friday)
2. Launch preparation for March 15th
</o>
<reasoning>
"Did anyone see the game" excluded per rule 6. Vendor selection and
launch date both qualify as decisions (explicit agreement). Only Mike
has a named action item.
</reasoning>
</example>
</examples>
<context>
{{transcript}}
</context>Why it works for Haiku
- Five sections with exact formatting prevents structural drift
- Action item format is fully specified (person — task — deadline)
- Rule 4 distinguishes decisions from proposals (Haiku would conflate them)
- Rule 5 handles unassigned actions with explicit default
- Example excludes off-topic content, demonstrating rule 6 in practice