1c538567f6
New skill: meeting-minutes-taker - Transform meeting transcripts into structured minutes - Multi-pass parallel generation with UNION merge - Evidence-based recording with speaker quotes - Mermaid diagrams for architecture discussions - Iterative human-in-the-loop refinement - Bundled references: template and completeness checklist skill-creator enhancements: - Add Step 5: Sanitization Review (Optional) - New references/sanitization_checklist.md with: - 8 categories of content to sanitize - Automated grep scan commands - 3-phase sanitization process - Common pitfalls and completion checklist - Renumber existing steps 5-8 to 6-9 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
100 lines
3.7 KiB
Markdown
100 lines
3.7 KiB
Markdown
# Meeting Minutes Review Checklist
|
|
|
|
## Contents
|
|
- Completeness Review Process (4 phases: structural, content depth, quotes, action items)
|
|
- Common Omission Patterns (technical, business logic, process items)
|
|
- Merge Strategy (multi-version union rules)
|
|
- Red Flags (signs of missing content)
|
|
|
|
## Completeness Review Process
|
|
|
|
### Phase 1: Structural Check
|
|
|
|
- [ ] All major discussion topics from transcript are covered
|
|
- [ ] Each decision has supporting quote
|
|
- [ ] All speakers who made decisions are attributed
|
|
- [ ] Action items have specific owners (not generic "team")
|
|
- [ ] Priorities assigned to all action items
|
|
|
|
### Phase 2: Content Depth Check
|
|
|
|
For each transcript section, verify:
|
|
|
|
- [ ] **Entities/Data Models**: All mentioned entities captured (tables, fields, relationships)
|
|
- [ ] **Numerical Values**: Ranges, priorities, counts preserved (e.g., "0-99", "4 states", "3-4 categories")
|
|
- [ ] **State Machines**: All states and transitions documented
|
|
- [ ] **Architecture Decisions**: Data flow, dependencies, integration points
|
|
- [ ] **Trade-offs**: Rejected alternatives and reasoning
|
|
- [ ] **Constraints**: Technical limitations, MVP scope boundaries
|
|
|
|
### Phase 3: Quote Verification
|
|
|
|
For significant decisions, ensure:
|
|
|
|
- [ ] Quote accurately reflects speaker's point
|
|
- [ ] Speaker attribution is correct
|
|
- [ ] Context around quote is preserved
|
|
|
|
### Phase 4: Action Items Audit
|
|
|
|
Cross-reference with transcript for:
|
|
|
|
- [ ] Explicit task assignments ("Alice will handle...", "Bob, please...")
|
|
- [ ] Implicit commitments ("I will design...", "Backend team will...")
|
|
- [ ] Deferred items ("Defer to later...", "Not in MVP scope...")
|
|
- [ ] Follow-up discussions needed ("Discuss offline...", "Follow up separately...")
|
|
|
|
## Common Omission Patterns
|
|
|
|
### Technical Details Often Missed
|
|
|
|
1. **Entity Hierarchies**: Category → Subcategory → Item → Detail
|
|
2. **Field Definitions**: What fields belong to which entity
|
|
3. **Calculation Rules**: Priority orders, workflow logic, matching rules
|
|
4. **Storage Decisions**: Where data is persisted, what's cached
|
|
5. **API Contracts**: Who calls whom, sync vs async
|
|
|
|
### Business Logic Often Missed
|
|
|
|
1. **State Transitions**: What triggers state changes
|
|
2. **Permission Rules**: Who can do what
|
|
3. **Validation Rules**: Required fields, constraints
|
|
4. **Display Logic**: What's shown where, sorting rules
|
|
5. **Integration Points**: Cross-system data sharing
|
|
|
|
### Process Items Often Missed
|
|
|
|
1. **Design Approach**: Joint vs separate design decisions
|
|
2. **Dependency Order**: What blocks what
|
|
3. **Offline Follow-ups**: Items requiring separate discussion
|
|
4. **Scope Deferrals**: What's explicitly pushed to Phase 2
|
|
|
|
## Merge Strategy (Multi-Version Union)
|
|
|
|
When merging versions:
|
|
|
|
1. **Keep ALL content from existing version** - Never remove unless explicitly wrong
|
|
2. **Add NEW content from incoming version** - Union, not replace
|
|
3. **Resolve conflicts by combining** - Include both perspectives
|
|
4. **Preserve more detailed version** - When same topic has different depth
|
|
5. **Maintain structure** - Keep section numbering logical
|
|
|
|
### Merge Checklist
|
|
|
|
- [ ] All sections from original preserved
|
|
- [ ] All sections from new version added (or merged into existing)
|
|
- [ ] No duplicate content (consolidate if same info appears twice)
|
|
- [ ] Quotes from both versions preserved
|
|
- [ ] Action items from both versions merged
|
|
- [ ] Numbering remains sequential
|
|
|
|
## Red Flags (Signs of Missing Content)
|
|
|
|
- Transcript mentions a topic not in minutes
|
|
- Decision recorded without quote
|
|
- Action item without clear owner
|
|
- Long transcript section summarized in one sentence
|
|
- Technical discussion with no entity/field names
|
|
- "TBD" items without clear description
|
|
- State machine with fewer states than mentioned
|
|
- Priority/order system without number ranges |