documenting-meetingslisted

# Skill: documenting-meetings ## Purpose This skill transforms an SRT audio transcript into structured meeting notes with decisions, action items, and discussion summary. - **Input:** `audio.srt` file — path supplied by the user - **Output:** `summary.md` written to the output directory supplied by the user (default: `./meeting-notes/`) - **When to use:** after any team meeting that was recorded and has a transcript - **When NOT to use:** for meetings without a transcript (no audio.srt) --- ## Pre-checks - Verify `audio.srt` exists at the path the user supplied - Check for any supporting files in the same directory (screenshots, diagrams, linked files) — if present, review them for context before reading transcript - If a team roster or speaker-login map is available (e.g. a team doc), load it to identify speakers by login - Confirm meeting date and name from the path or user input --- ## Workflow 1. If a team roster exists, read it to map speaker logins to names and roles 2. Check the meeting directory for any supporting materials (screenshots, diagrams, linked files) — note them for use in verification 3. Read the full `audio.srt` transcript 4. Identify all speakers and their contributions 5. Extract: objective, decisions made, action items (with owner and deadline), key discussion points, hidden motivations, open issues, next steps 6. Verify technical claims: for any specific technical fact (field name, system behavior, numeric claim), check against supporting fil