What It Does
It follows a strict 12-section schema covering metadata, attendance, decisions, action items (with owners and due dates), parking lot items, risks, and references. Output is designed to be immediately actionable and easy to import into task trackers like GitHub Issues or Jira.
Meeting Minutes is a skill that transforms raw meeting inputs — transcripts, recordings, notes, or live captures — into consistent, high-quality minutes documents.
Key Features
- Strict 12-Section Minutes Schema — Every output follows a fixed structure: Metadata, Attendance, Agenda, Summary, Decisions, Action Items, Notes by Agenda Item, Parking Lot, Risks/Blockers, Next Meeting, Attachments, and a Version/Change Log. This ensures nothing is omitted and every document is consistent across your team.
- Action Items with Owner, Due Date & Acceptance Criteria — Each action item is recorded in a structured format including a unique ID, owner name and team, due date (ISO 8601), and acceptance criteria. Optional links to tickets or artifacts provide full traceability back to your project tracker.
- Guided Intake with Clarifying Questions — Before drafting, the skill identifies missing critical fields (title, date, organizer, source material) and asks up to three targeted clarifying questions. If no transcript or agenda is available, it proceeds from ad-hoc notes and flags potential gaps explicitly.
- Multi-Source Input Support — Minutes can be generated from a meeting transcript, a recording summary, an agenda with slide deck, or unstructured raw notes. The source type is recorded in the document metadata for auditability.
- Parking Lot & Risk Tracking — Unresolved issues are captured in a dedicated Parking Lot section with suggested owners and next steps. Risks and blockers are listed separately with impact notes and mitigation owners — keeping follow-up accountable.
- Task-Tracker Ready Output — The structured action items and decisions are formatted to be directly convertible into GitHub Issues, Jira tickets, or similar tools, reducing the manual work of translating minutes into tasks.
Use Cases
- Weekly Engineering Sync — Paste the transcript from a 45-minute platform sync and the skill generates full minutes with all decisions labeled, action items assigned to engineers by name, and links to relevant GitHub issues — ready to post in your team channel within minutes.
- Design Review Documentation — Provide rough notes from a 30-minute feature design review. The skill asks up to three clarifying questions for any missing fields, then produces a concise document highlighting design decisions, open questions in the Parking Lot, and next steps for the designer and engineering lead.
- Sprint Planning or Triage Meeting — Feed in an agenda and live notes from a sprint planning session. The skill captures prioritization decisions, assigns ticket owners and due dates, and logs any deferred items with rationale — creating an audit trail for the sprint.
- Ad-Hoc Standup or Incident Sync — Even without an agenda or transcript, the skill can produce useful minutes from bullet-point notes, clearly marking uncertain items as `TBD` and flagging what additional information should be gathered before the document is distributed.