{
  "schema_version": 2,
  "kind": "shortening-method",
  "format": "agent-skill",
  "id": "meeting-notes",
  "name": "Meeting notes",
  "category": "Work",
  "summary": "Separate discussions, decisions, tasks, and unresolved risks.",
  "use_cases": [
    "Meeting transcripts",
    "Project check-ins",
    "Decision records"
  ],
  "word_count": 110,
  "url": "https://sho.rten.it/methods/meeting-notes/",
  "instructions_url": "https://sho.rten.it/methods/meeting-notes/SKILL.md",
  "skill_url": "https://sho.rten.it/methods/meeting-notes/SKILL.md",
  "json_url": "https://sho.rten.it/methods/meeting-notes/llms.txt",
  "plain_text_url": "https://sho.rten.it/methods/meeting-notes/prompt.txt",
  "license": "MIT",
  "sources_url": "https://sho.rten.it/sources/#meeting-notes",
  "skill_name": "meeting-notes",
  "skill_description": "Separate discussions, decisions, tasks, and unresolved risks. Use for Meeting transcripts, Project check-ins, Decision records.",
  "agents_md_url": "https://sho.rten.it/methods/meeting-notes/AGENTS.md",
  "sources": [
    {
      "title": "Fabric · summarize_meeting",
      "url": "https://github.com/danielmiessler/Fabric/blob/b682dad740f24e85ce9a48d23babc6780dd476ac/data/patterns/summarize_meeting/system.md",
      "repository": "https://github.com/danielmiessler/Fabric",
      "revision": "b682dad740f24e85ce9a48d23babc6780dd476ac",
      "path": "data/patterns/summarize_meeting/system.md",
      "license": "MIT",
      "license_url": "https://github.com/danielmiessler/Fabric/blob/b682dad740f24e85ce9a48d23babc6780dd476ac/LICENSE",
      "license_file": "licenses/danielmiessler--fabric.txt",
      "copyright": "Copyright (c) 2012-2024 Scott Chacon and others",
      "repository_stars": 43885,
      "checked_at": "2026-09-11T05:14:00Z",
      "license_scope": "Root MIT license covers this pinned prompt. No nested license or NOTICE applies.",
      "adaptation": "Retains all eight sections, overview limit, action owners/deadlines, and concise bullets. Replaces minimum item counts and exact 16-word padding with content-supported items."
    }
  ],
  "instructions": "Turn the supplied meeting transcript into concise Markdown notes.\n\nUse these sections: OVERVIEW, KEY POINTS, TASKS, DECISIONS, CHALLENGES, TIMELINE, REFERENCES, and NEXT STEPS. Keep the overview within 25 words and include the meeting's purpose and named participants when available.\n\nCapture the important discussion points, every assigned task, confirmed decisions, risks, dates, mentioned resources, and follow-up work. Include owners and deadlines only when stated. Distinguish a proposal from a decision and an unassigned action from an assigned task.\n\nUse short bullets, usually no more than 16 words. Avoid repeating an item across sections. Write \"Not stated\" for missing information. Do not invent tasks to fill a section or a target count.",
  "example": {
    "context": "Release-readiness meeting with two assigned tasks",
    "before": "Mia and Jules met to decide whether the release was ready. Jules reported that the backup restore test had failed twice; they did not yet know why. They agreed to delay the launch. Mia committed to investigate the restore failure by Friday, and Jules said he would attach the two failed-test logs to the incident ticket today. They agreed to use the backup runbook during the investigation. They did not choose a new release date. Mia suggested meeting again after the investigation to review the results, and Jules agreed, but they did not schedule that meeting.",
    "after": "OVERVIEW\nMia and Jules reviewed release readiness.\n\nKEY POINTS\n- The backup restore test failed twice.\n\nTASKS\n- Mia investigates the restore failure by Friday.\n- Jules attaches both failed-test logs to the incident ticket today.\n\nDECISIONS\n- Delay the launch.\n\nCHALLENGES\n- Restore failure cause remains unknown.\n\nTIMELINE\n- New release date: Not stated.\n\nREFERENCES\n- Backup runbook; incident ticket.\n\nNEXT STEPS\n- Meet after the investigation to review results. Meeting date: Not stated.",
    "must_preserve": [
      "Mia and Jules; release-readiness purpose",
      "Two restore failures; unknown cause",
      "Confirmed launch delay",
      "Mia investigation due Friday; Jules attaches both logs today",
      "Backup runbook and incident ticket",
      "Release date absent; follow-up agreed after investigation but unscheduled"
    ],
    "omitted": [
      "Removes dialogue framing and avoids repeating tasks under next steps. Missing dates are marked without inventing deadlines."
    ],
    "kind": "illustrative"
  }
}