Skip to main content
Back to Library
Prompt Engineering Guide

Mastering Meeting notes extraction
on Command R+

Stop guessing. See how professional prompt engineering transforms Command R+'s output for specific technical tasks.

The "Vibe" Prompt

"Extract the key decisions, action items, and next steps from the following meeting transcript. Make it concise."
Low specificity, inconsistent output

Optimized Version

STABLE
You are an expert meeting summarizer. Your goal is to extract structured information from a meeting transcript. Here is the process you must follow to ensure accuracy and completeness: 1. **Identify Key Decisions**: Read through the transcript specifically looking for final agreements, approvals, or conclusions reached by the participants. Note the decision itself and the people involved or responsible. 2. **Extract Action Items**: Scan the transcript for tasks assigned to specific individuals or teams, along with deadlines if mentioned. Ensure each action item clearly states 'who' will do 'what' by 'when' (if applicable). 3. **Summarize Next Steps**: Consolidate any planned future actions, follow-ups, or upcoming meetings that were discussed as a continuation of the current discussion. 4. **Consolidate and Format**: Group the identified information under clear headings: 'Key Decisions', 'Action Items', and 'Next Steps'. For each item, provide a brief, clear, and actionable statement. Meeting Transcript: [Insert Meeting Transcript Here] Provide the output in the following structured format: Key Decisions: - [Decision 1] - [Decision 2] Action Items: - [Owner]: [Task] (due: [Date/Time, if specified]) - [Owner]: [Task] Next Steps: - [Next Step 1] - [Next Step 2]
Structured, task-focused, reduced hallucinations

Engineering Rationale

The optimized prompt leverages several best practices for instruction tuning. First, it assigns a persona ('expert meeting summarizer') to the model, which can improve performance. Second, it breaks down the complex task of 'meeting notes extraction' into a sequential, numbered chain-of-thought process, guiding the model step-by-step. This clarity reduces ambiguity and ensures all required components are addressed. Third, it explicitly defines the desired output format with examples, minimizing the model's need to infer structure and thus reducing errors. The structured schema significantly improves the consistency and quality of the extracted information compared to the vague 'make it concise' instruction in the naive version.

0%
Token Efficiency Gain
The output for 'Key Decisions' should precisely match final agreements in the transcript.
Each 'Action Item' must include an assignee and a clear task description.
All mentioned 'Next Steps' from the transcript must be captured under that heading.

Ready to stop burning tokens?

Join 5,000+ developers using Prompt Optimizer to slash costs and boost LLM reliability.

Optimize My Prompts