vibepro-meeting-minutes-editorlisted

# VibePro Meeting Minutes Editor ## Purpose Use this Skill to turn meeting source material into an edited business document, not a shallow transcript summary. The output should read like a usable executive meeting note: it explains the strategic context, the stakes, the real decisions, and the next moves in language that someone absent from the meeting can act on. ## When to Use Use this Skill when the user asks for 議事録, meeting notes, Meeting Pack output, transcript summarization, Slack-attached meeting material, or a quality review of generated minutes. Use it especially when the user provides exemplar minutes and expects the agent to reverse-engineer the writing standard instead of forcing the output into a fixed package template. ## Required Workflow 1. Confirm source completeness before writing. - Check whether the transcript, attached files, recording-derived text, chat context, and referenced Slack thread are actually available. - If transcript or attachment retrieval failed, mark the note as blocked or incomplete. Do not fill the gap with generic topics or task candidates. 2. Infer the meeting type before choosing structure. - Strategy / negotiation / sales / project governance / marketing operations / technical planning each need different sectioning. - Do not force every meeting into `Core Synopsis`, `Action Items`, or any single package shape. 3. Write the opening as an edited synopsis. - Explain what the meeting was trying to settle, why it m