Stats
Actions
Tags
From aigroup-workflow
Structures meeting notes with templates for decisions, action items, and follow-ups following PM best practices.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aigroup-workflow:meeting-notesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill structures meeting notes to maximize value and ensure follow-through.
This skill structures meeting notes to maximize value and ensure follow-through.
Meeting: [Meeting Title]
Date: [Date]
Attendees: [Names/Roles]
Note Taker: [Name]
Duration: [Actual duration]
(Check off items as discussed)
Clear documentation of decisions:
Decision: [What was decided]
Context: [Why this decision]
Owner: [Who's responsible for executing]
Deadline: [When if applicable]
Use this format for each decision made.
All action items should be:
Format:
Key points discussed organized by topic:
Topic 1: [Name]
Topic 2: [Name]
Questions that couldn't be answered:
Clear summary of what happens next:
During the meeting:
After the meeting:
What to capture: ✅ Decisions made ✅ Action items with owners and deadlines ✅ Key points of discussion ✅ Open questions ✅ Next steps
What to skip: ❌ Verbatim transcripts ❌ Off-topic tangents ❌ Preliminary discussion before decisions ❌ Redundant information
Focus on:
Template additions:
Focus on:
Template additions:
Focus on:
Template additions:
Focus on:
Template additions:
# Product Roadmap Review - Q1 2026
**Date**: January 20, 2026
**Attendees**: Sarah (CPO), Mike (Eng Lead), Jennifer (Design), Tom (PM)
**Note Taker**: Tom
**Duration**: 45 minutes
## Agenda
- [x] Review Q1 planned features
- [x] Discuss resource constraints
- [x] Prioritization discussion
- [x] Timeline alignment
## Decisions Made
**Decision**: Move multi-channel dashboard to Q2, prioritize mobile app improvements for Q1
**Context**: Customer feedback shows mobile experience is significantly impacting retention (65% of users primarily mobile). Engineering team can only tackle one major initiative this quarter.
**Owner**: Tom (PM) to communicate to stakeholders
**Deadline**: January 22
**Decision**: Allocate 20% of engineering time to technical debt
**Context**: Accumulated tech debt is slowing feature development. Team velocity dropped 30% last quarter.
**Owner**: Mike (Eng Lead) to create tech debt backlog
**Deadline**: January 27
**Decision**: Run mobile beta with 100 users before full launch
**Context**: Need to validate improvements on diverse devices
**Owner**: Jennifer (Design) to coordinate with QA
**Deadline**: February 10
## Action Items
- [ ] **Update Q1 roadmap deck with new prioritization** - @Tom - Due: Jan 22
- [ ] **Schedule alignment meeting with support team about dashboard delay** - @Tom - Due: Jan 24
- [ ] **Create tech debt prioritization rubric** - @Mike - Due: Jan 27
- [ ] **Run user testing on mobile designs** - @Jennifer - Due: Feb 3
- [ ] **Document decision rationale for executives** - @Sarah - Due: Jan 23
- [ ] **Identify 100 beta users for mobile** - @Tom - Due: Feb 1
## Discussion Notes
**Q1 Feature Prioritization**
- Customer retention is #1 company priority this quarter
- Mobile app NPS score is 6.2 (vs 8.1 for web)
- Mobile accounts for 65% of daily active users
- Multi-channel dashboard would take 8 engineering weeks
- Mobile improvements estimated at 6 engineering weeks with higher ROI
- Sales has 3 enterprise deals waiting on dashboard feature
**Resource Constraints**
- Currently 4 engineers available (down from 6 last quarter due to attrition)
- Design team can support both initiatives but at reduced capacity
- QA team needs 2 weeks for thorough testing on mobile
- One engineer on loan to security team through February
**Risk Discussion**
- Delaying dashboard may impact enterprise sales (3 deals waiting)
- Sarah noted: "We can position mobile improvements as foundation for enterprise features"
- Mike raised concern about mobile tech stack stability - addressed through tech debt allocation
- Need to communicate clearly with Sales about timeline change
**Mobile Implementation Plan**
- Week 1-2: Design refinements based on user feedback
- Week 3-4: Engineering implementation
- Week 5: Internal testing
- Week 6: Beta with 100 users
- Week 7: Full rollout
## Open Questions
- **Question**: What's the impact on enterprise pipeline if we delay dashboard?
**Owner**: Sarah will check with Sales leadership
**By When**: January 23
- **Question**: Can we do a limited beta of dashboard for enterprise customers?
**Owner**: Tom will explore MVP scope with Mike
**By When**: January 25
- **Question**: What's our plan if mobile improvements don't hit target metrics?
**Owner**: Tom will create contingency plan
**By When**: January 27
## Next Steps
1. Tom to send updated roadmap to leadership by EOD Wednesday (Jan 22)
2. Team to begin sprint planning for mobile improvements next Monday (Jan 27)
3. Follow-up meeting on Feb 1 to review progress and validate prioritization
4. Sarah to present decision rationale to executive team on Jan 24
---
**Next Meeting**: February 1, 2026 - Progress Check-in
**Notes Sent**: January 20, 2026 5:30 PM
Subject Line Format: "[Meeting Type] Notes - [Date] - [Key Topic]"
Example: "Product Roadmap Review Notes - Jan 20 - Q1 Prioritization"
Recipients:
Follow-Up:
npx claudepluginhub codeape-7/ai-agent-workflowgroupStructures and formats meeting notes using PM best practices with templates for agendas, decisions, action items, discussions, and next steps. Useful for capturing outcomes from meetings like 1:1s or sprint planning.
Generates structured Markdown meeting notes from discussions, with attendees, agenda, key points, decisions, action items, metrics tables, and follow-ups.
Generates structured meeting agendas by gathering context from previous summaries, external services (GitHub, Slack via TECH.md), and custom templates. Automatically detects missing summaries and guides generation.