track-meeting

Track Meeting Skill

When to use this Skill

Activate when the user:

• Mentions creating or recording meeting notes
• Uses keywords: "meeting", "standup", "retrospective", "planning", "review"
• Wants to document a team discussion
• Needs to track meeting action items
• References specific meeting types (daily standup, sprint planning, etc.)

Workflow

Phase 1: Context Discovery

Objective: Understand the project context and meeting format requirements.

Steps:

1. Locate project RULE.md:

   # Check current directory
   ls RULE.md
   # If not found, check parent directories
   ls ../RULE.md
   ls ../../RULE.md
   

2. Read RULE.md using Read tool:

   • Extract methodology field (determines meeting types)
   • Find Document Templates > Meeting Notes Format section
   • Note file_naming_convention pattern
   • Check meetings/ directory structure
   • Read Auto Workflows > When Claude creates meeting notes section

3. Determine meeting types available based on methodology:

   • Scrum: daily-standups, sprint-planning, sprint-reviews, retrospectives, general
   • Kanban: board-reviews, planning, general
   • Waterfall: phase-reviews, status-updates, general
   • Agile/Hybrid: planning, reviews, general

4. Check existing meetings directory:

   ls -la meetings/
   

   Understand the current structure and recent meetings.

5. Read meetings/README.md if exists:

   • Understand current meeting index
   • Note recent meetings for context

Example:

Found RULE.md:
- Methodology: Scrum (2-week sprints)
- Meeting types: daily-standups, sprint-planning, sprint-reviews, retrospectives
- Format: Structured with YAML frontmatter
- Naming: Date-prefixed (YYYY-MM-DD_meeting-name.md)
- Directory: meetings/{type}/

Phase 2: Gather Meeting Details

Objective: Collect all necessary information about the meeting.

Steps:

1. Extract from user message (if provided):
   • Meeting type (standup, planning, etc.)
   • Date (today if not specified)
   • Meeting title or topic