weekly-minutes

Generate structured weekly retrospective minutes from sprint notes and VTT transcripts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/vitalwarley/hyprdots --skill weekly-minutes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-minutes
Source: https://github.com/vitalwarley/hyprdots/tree/main/claude-global/skills/weekly-minutes
Command: npx skills add https://github.com/vitalwarley/hyprdots --skill weekly-minutes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates a lead's sprint issue live notes with a VTT transcript to produce a single, structured weekly retrospective (ata) in Portuguese, removing manual consolidation and ensuring decisions and action items are highlighted.

Core Features & Use Cases

  • Authoritative source merging: Treats the lead's live notes as the base and enriches them with exact quotes and nuance from the VTT transcript.
  • ASR-aware parsing: Applies team-specific ASR corrections to improve transcript accuracy and attribution.
  • Cross-references project context: Reads dailies, sprint planning, and issue states to surface recurring blockers, closed work, and deviations from plan.
  • Output & posting: Writes a retrospective-formatted ata to the configured output path and updates the sprint issue with a brief summary and link.
  • Use case: Prepare a Portuguese retrospective at the end of a sprint by merging the sprint issue notes and meeting transcript, then post a concise summary on the sprint issue.

Quick Start

Generate weekly minutes for sprint issue #85 using docs/meetings/weekly.vtt dated 2026-03-28 for sprint-4 week-2.

Frequently Asked Questions about weekly-minutes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate weekly meeting minutes from VTT transcripts and sprint notes?

Generate structured weekly meeting minutes by merging a lead's sprint issue live notes with a VTT transcript. The lead's notes serve as the authoritative base, enriched with exact quotes and tone parsed from the VTT file.

What is the best way to consolidate VTT transcript files with sprint issue live notes?

Consolidating VTT transcripts with sprint notes involves cross-referencing project context like dailies and planning, then applying team-specific ASR corrections to the transcript to improve quote accuracy and speaker attribution before merging.

Can I use ASR corrections to improve VTT transcript accuracy for sprint retrospectives?

Yes, you can apply team ASR corrections to VTT transcripts. This ASR-aware parsing mechanism corrects automated speech recognition errors, ensuring that the exact quotes and nuance added to your sprint retrospective minutes are accurate.

How to post a retrospective summary and link directly to a GitHub sprint issue?

To post a retrospective summary to a GitHub sprint issue, generate the structured minutes from your notes and VTT file, write the full retrospective to your configured output path, and update the sprint issue comments with a brief summary and link.

Does generating sprint retrospective minutes require access to project context like dailies?

Yes, generating accurate sprint retrospective minutes requires access to sprint issue content, the VTT file, team ASR corrections, and project context like dailies and planning to surface recurring blockers, closed work, and deviations from plan.

Why does my retrospective summary need team ASR corrections applied to the VTT file?

Team ASR corrections are needed for VTT files to fix automated speech recognition errors specific to your team's vocabulary. Applying these corrections ensures the exact quotes and nuance enriched into your meeting minutes are properly attributed and accurate.