Este prompt de IA convierte notas de reuniones desordenadas en resúmenes accionables
Why this prompt matters
Unprocessed meeting notes are a primary source of team misalignment and missed deadlines. Ambiguity about 'who does what by when' costs companies hours of rework and follow-up. This prompt eliminates that ambiguity, saving an average of 30-60 minutes per meeting and creating a reliable source of truth for all stakeholders.
What we use it for
You are a Project Manager who just finished a chaotic weekly sync with the engineering and marketing teams. You have a raw transcript full of cross-talk and side conversations. Instead of spending 45 minutes manually creating a summary, you use this prompt to generate a clean, structured report in under two minutes, ready to be pasted into Slack or email.
Prompt
Act as an expert project manager and professional scribe. Your task is to transform the raw, unstructured meeting transcript provided below into a clear, concise, and actionable summary. Your output must be well-organized, easy to read, and optimized for team communication and follow-up. **CONTEXT:** This transcript is from the [MEETING NAME OR TOPIC] meeting held on [DATE]. The primary goals of this meeting were to [GOAL 1], [GOAL 2], and [GOAL 3]. The attendees included [LIST OF KEY ATTENDEES OR TEAMS]. **TASK:** Analyze the provided transcript and produce a structured summary that includes the following four distinct sections: 1. **Executive Summary:** A brief, one-paragraph overview of the meeting's key discussions, outcomes, and overall sentiment. 2. **Key Decisions Made:** A numbered list of all concrete decisions that were finalized during the meeting. For each decision, clearly state what was decided. 3. **Action Items:** A bulleted list of all tasks that were assigned. Each item must be formatted as: `[ASSIGNEE'S NAME] - [SPECIFIC ACTION TO BE TAKEN] - (Due: [YYYY-MM-DD])`. If a due date is not mentioned, use 'TBD'. 4. **Open Questions & Parking Lot:** A bulleted list of important questions that were raised but not answered, or topics that were deferred for a future discussion. **CONSTRAINTS:** - Do not include conversational filler or off-topic chatter. - Extract and synthesize; do not simply copy and paste sentences from the transcript. - Be objective and neutral in your summary. - If an assignee or due date is unclear, make a reasonable inference and note it (e.g., 'Team Lead?' or 'Due: TBD'). - The final output must be in Markdown format. **OUTPUT FORMAT:** ### Meeting Summary: [MEETING NAME] **1. Executive Summary** [Your one-paragraph summary here.] **2. Key Decisions Made** 1. [Decision 1] 2. [Decision 2] **3. Action Items** - [ASSIGNEE] - [ACTION] - (Due: [YYYY-MM-DD]) - [ASSIGNEE] - [ACTION] - (Due: [YYYY-MM-DD]) **4. Open Questions & Parking Lot** - [Question 1] - [Question 2] **TRANSCRIPT TO ANALYZE:** ``` [PASTE YOUR RAW MEETING TRANSCRIPT HERE] ```
Result
### Meeting Summary: Project Phoenix - Q3 Feature Launch Sync
*1. Executive Summary*
The Q3 feature launch sync for Project Phoenix focused on finalizing the go-to-market strategy and addressing the critical backend scaling issue identified last week. The marketing team presented a revised campaign timeline, which was approved with minor adjustments. A significant decision was made to delay the international launch by two weeks to allow the engineering team to implement and test a new caching solution. Several key action items were assigned to both teams to ensure alignment and prevent further delays.
**2. Key Decisions Made** 1. The revised marketing campaign timeline proposed by Sarah is approved. The official launch date for the US market is now set for August 15th, 2026. 2. The international launch (EMEA & APAC) will be postponed from September 1st to September 15th, 2026. 3. Engineering will proceed with implementing the 'Helios' caching system as the primary solution for the backend scaling problem. 4. The budget for supplemental QA testing is approved, with an additional $15,000 allocated to the project.
**3. Action Items** - **Sarah (Marketing)** - Update the master project GANTT chart to reflect the new campaign and launch dates. - (Due: 2026-04-28) - **Mark (Engineering)** - Deliver a full technical spec and implementation plan for the Helios caching system. - (Due: 2026-05-01) - **David (QA)** - Onboard the external QA contractors and get them integrated with the team's testing environment. - (Due: 2026-04-30) - **Chen (Backend Engineering)** - Complete the initial stress tests on the new staging environment with the Helios prototype. - (Due: 2026-05-05) - **Maria (Product)** - Draft the internal and external communications announcing the revised launch dates. - (Due: 2026-04-29)
**4. Open Questions & Parking Lot** - What is the final plan for localizing the campaign assets for the APAC market? (Sarah to follow up with the regional team). - Do we have a definitive answer on whether the new caching system will affect API response times for our enterprise partners? (Mark to investigate). - The topic of redesigning the user onboarding flow was raised but deferred to the next product-specific meeting.
Las reuniones son esenciales, pero la carga administrativa de procesar las notas puede ser un gran lastre para la productividad. Las transcripciones sin procesar suelen ser una mezcla caótica de diálogos, interrupciones e ideas sin desarrollar. Este prompt está diseñado para eliminar el ruido, proporcionando un resumen claro, estructurado y útil de inmediato que se puede compartir con el equipo.
Funciona indicándole a la IA que actúe como un gestor de proyectos profesional, analizando sistemáticamente el contenido, identificando la información más crítica y organizándola en un formato estandarizado. Al definir una estructura clara con secciones específicas para un resumen, decisiones clave, tareas asignadas y preguntas abiertas, garantizas una salida consistente y de alta calidad en cada uso.