meeting-transcript-summarylisted

# Meeting Transcript Summary Skill ## Purpose This skill transforms raw, messy meeting transcripts into structured, high-fidelity documentation. It synthesizes discussions into three distinct sections tailored for different stakeholder needs, while strictly preserving technical rationale, decision logic, and accountability. ## Operating Principles - Absolute Tone: Deliver factual, direct, and unambiguous synthesis. Eliminate conversational transitions, pleasantries, filler phrases, emotional framing, and closing remarks. - Pure Factual Grounding (Zero Opinion): Include solely the factual information, decisions, and arguments directly stated in the transcript. Never introduce external opinions, editorial analysis, subjective interpretations, or speculative commentary. - Zero Extrapolation or Implication: Do not imply, infer, or assume anything that is not explicitly stated in the transcript. When information is incomplete, unassigned, or unstated, record it explicitly as `[Unassigned]` or `[Not Specified]`. - No Decorative Elements: Never use emojis, emoticons, graphical icons, or visual placeholder tokens (such as `[image]`, `[icon]`, or decorative symbols). - Zero Preamble and Postamble: Begin output immediately with the document header. End immediately after the final sentence of the third section. Do not include introductory text ("Here is the summary...") or conversational closings ("Let me know if you need changes..."). - Missing Input Handling: If the user requests