summarize-meeting

To extract action items and decisions from meeting transcripts, you need a transcript file, project context, and existing tasks.md. The Skill analyzes the transcript to identify tasks, owners, due dates, and decisions for traceability.

Yes, you can automatically route meeting action items to GitHub Issues and tasks.md. It classifies items based on estimated effort and project context, sending quick tasks to tasks.md and longer tasks to GitHub Issues.

You need a transcript file stored under .research/meetings/transcripts, a project context file, and an existing tasks.md file. The Skill uses these inputs to output a structured summary and optional GitHub Issues for longer tasks.

Transcript summarization classifies items into tasks or issues by analyzing the transcript content alongside project context. It evaluates the estimated effort and complexity of each action item to route it appropriately.

To capture key points and outcomes from lab meetings for the next sprint, use the Skill to generate a structured summary from your transcript. It identifies decisions and populates task lists based on the meeting outcomes.

No, meeting transcript summarization requires a project context file to classify items accurately. It uses the project context to determine whether an action item should become a quick task or a GitHub Issue.