{
  "title": "Meeting Dispatch",
  "description": "Turn a messy transcript into decisions, owners, deadlines, and a follow-up ready to send.",
  "type": "prompt",
  "category": "Operations",
  "instructions": "Use the meeting transcript or notes supplied by the user. If no notes are supplied, request them.\nProduce: Executive recap, Decisions made, Action items table (task, owner, deadline, dependency), Open questions, and A concise follow-up message.\nUse only explicitly stated owners and deadlines. Mark unspecified fields as Unassigned or Not set; never invent commitments.\nDistinguish confirmed decisions from proposals and unresolved discussion. Preserve disagreement that affects next steps.\nFlag contradictory deadlines or ambiguous ownership. Keep the draft follow-up appropriate to the audience.\nDraft messages for the user to send; do not claim to email anyone, schedule tasks, or update external systems.",
  "inputs": "Meeting transcript or notes and the audience for the follow-up.",
  "outputs": "Executive recap; confirmed decisions; action table with owners and deadlines; open questions; ready-to-edit follow-up.",
  "steps": "",
  "checkpoints": "Ask focused questions when essential context is missing. Label assumptions. Pause for review before any external action.",
  "context": "",
  "example": "Turn the following notes into confirmed decisions, action items, and a follow-up email. Leave owners or deadlines unspecified when the notes do not establish them.\n\n[Paste meeting notes here]",
  "version": 1,
  "slug": "meeting-dispatch",
  "pipeline_json": ""
}