promptsDBText Analysis & GenerationProductivitySummarization
Turn Meeting Transcript Into Action Plan
Convert meeting transcripts into a concise action plan with decisions, owners, due dates, priorities, metrics, risks, and open questions, inferring missing owners/dates and labeling assumptions.
Prompt Content
Create a concise action plan from the meeting transcript, highlighting decisions, owners, and next steps.
1) Read the transcript in
<transcript>
Transcript
</transcript>
.
2) Extract explicit decisions; merge duplicates; add brief rationale when stated or (Assumed) if inferred.
3) Build an action plan with clear tasks, owners, due dates, priority, status, dependencies, and success metrics.
4) Assign owners from the transcript; if missing, infer best-fit owner from roles; otherwise mark Unassigned (Proposed: Name).
5) Set due dates: use dates stated in the transcript; if missing, suggest realistic ISO dates (YYYY-MM-DD) relative to Reference Date (High: 3-5 business days; Medium: 1-2 weeks; Low: 2-4 weeks).
6) List key risks/assumptions and open questions blocking progress.
7) Output using the exact structure below.
Constraints:
• Summary max 2 sentences
• Action Plan max 10 items
• Use only transcript facts; label any inference as (Assumed)
• No extra commentary or sections
Output structure:
Summary:
[1-2 sentences]
Decisions:
• Decision: [what] - Rationale: [why or Assumed] - Owner: [name or Unassigned (Proposed: X)] - Date: [YYYY-MM-DD or N/A]
Action Plan:
1) Task: [what]; Owner(s): [name(s)]; Due: [YYYY-MM-DD]; Priority: [High/Medium/Low]; Status: Not started; Dependencies: [if any]; Success metric: [how we know it's done]
[2)... up to 10]
Risks/Assumptions:
• [item]
Open Questions:
• [item]
<example>
Decisions:
• Decision: Adopt Option B for Q4 rollout - Rationale: lower risk - Owner: Product Lead - Date: 2025-11-10
Action Plan:
1) Task: Draft rollout plan v1; Owner(s): Maya Patel; Due: 2025-11-15; Priority: High; Status: Not started; Dependencies: decision on feature scope; Success metric: plan approved by leadership
</example>
Variables
- Transcript
- Full meeting transcript text, including participants, discussion, decisions, and any stated dates or owners
- Example: Attendees: Maya (PM), Alex (Eng Lead), Priya (Design)... Key points: We will adopt Option B... Alex to create API spec by next Friday...
- Reference Date
- Anchor date for scheduling due dates in ISO format (YYYY-MM-DD)
- Example: 2025-11-11