Transcript Processing Skill

Process the provided transcription following these steps:

Step 1: Create the Summary

Heading Format

1. •Check for date in filename or metadata (YYMMDD, YYYYMMDD, YYYY-MM-DD, etc.)
2. •Format: # Summary: [FILENAME] [DATE] - [MAIN TOPIC]
3. •If no date found: # Summary: [FILENAME] - [MAIN TOPIC]

Structure

• •Use --- to separate main sections
• •Use ## for section headings (sentence case)
• •Use bullet points for content within sections
• •Adapt section length to information relevance:
  • •Short sections: as little as 1 point if relevant
  • •Central topics: as many points as needed
• •End with "Next Steps" section when applicable

Content Rules

• •Identify and create headings for all distinct subject areas
• •Exclude personal reflections, sensitive information, private discussions
• •Prioritize concrete facts, business ideas, projects, technical details
• •Preserve key terms and technical terminology
• •Maintain original language throughout

Output Filename

Default format: YYMMDD-participant-topic-description.md Example: 250721-samtal-Tomas-Henrik-strategisk-genomgang.md

If the project has a CLAUDE.md that defines specific filename patterns (MEETING FILENAME FORMAT section), follow those conventions instead. For example, management 1-on-1s, weekly meetings, board meetings, and marketing meetings may each have their own naming pattern.

Step 2: Ask About File Organization

After creating the summary content, ask the user:

Where should I save this file?

Check for context clues and present options:

1. •CLAUDE.md routing (if available): Consult the project CLAUDE.md's MEETING ROUTING table and suggest the appropriate folder based on participants and topic detected in the transcript
2. •Participant folder (if detected): If =participant_name/ folders exist in the current directory, suggest the appropriate one
3. •Save to a specific path: Let user specify
4. •Just output the summary: Don't save to file

If both CLAUDE.md routing and =participant_name/ folders are available, present both suggestions and let the user choose.

If a CHANGELOG.md exists in the target location, offer to update it.

Step 3: CHANGELOG Update (if applicable)

If the user wants CHANGELOG updated and one exists:

If the project has domain-specific CHANGELOGs (consult CLAUDE.md), update the relevant one rather than a root CHANGELOG.

Entry Format

- **YYMMDD: Participant(s)** - ONE sentence summary of main topics. *(keyword1, keyword2, ... max 15 keywords)* -> [filename.md]

Rules

• •Add new entry at top of appropriate year section
• •Maximum 15 keywords in parentheses
• •ONE concise sentence (max 2 if absolutely necessary)
• •Include link to actual transcript file
• •Organize chronologically (newest first)

Structured Extraction (for Domain Skills)

When invoked by a domain skill (management-ops, marketing-ops, t1k-ops, project-ops), transcript can output structured data for further processing.

Extraction Format

extraction:
  date: YYYY-MM-DD              # From filename or content
  time: HH:MM                   # If mentioned
  duration: minutes             # If mentioned
  language: detected            # en/sv/mixed

participants:
  - name: string
    role: string                # If detected
    speaking_share: percentage  # Estimated

content:
  topics:
    - title: string
      summary: string
      participants: [names]
      importance: high/medium/low

  decisions:
    - decision: string
      rationale: string         # If provided
      owner: string             # If assigned
      deadline: string          # If mentioned

  action_items:
    - action: string
      owner: string
      deadline: string          # If mentioned
      priority: P0-P3           # If mentioned
      context: string           # Brief context

  issues:
    - issue: string
      reported_by: string
      severity: string          # If mentioned
      status: string            # open/resolved/blocked

  metrics:
    - name: string
      value: string
      context: string
      trend: up/down/stable     # If mentioned

  blockers:
    - blocker: string
      owner: string
      dependency: string        # External dependency

raw_summary: |
  # Traditional markdown summary
  (Full formatted summary as per Step 1)

Usage by Domain Skills

Domain skills can:

1. •Invoke transcript for extraction
2. •Receive structured YAML
3. •Apply domain-specific formatting
4. •Add domain-specific sections
5. •Execute configured workflows

This separation allows:

• •Consistent extraction logic across all skills
• •Domain skills focus on formatting and output
• •Easier testing and maintenance

Language

Always maintain the same language as the original transcription.