Skip to content

GuruDevvv/my-claude-skills / external/meeting-minutes-taker

meeting-minutes-taker

Verified

Transforms raw meeting transcripts into high-fidelity, structured meeting minutes (notes / summaries). Use when (1) a meeting transcript is provided and meeting minutes, notes, or a summary are requested; (2) multiple versions of minutes must be merged without losing content; (3) existing minutes need review against the original transcript for missing items; (4) the transcript has anonymous speakers like "Speaker 1/2/3" or "发言人1" that need identifying (optionally mapped via a context.md team directory). Triggers on 会议纪要 / 会议记录 / 整理纪要 / 妙记转纪要, "write meeting minutes", "summarize this meeting", "merge these minutes", "what's missing from these notes". For fixing ASR/STT recognition errors in the raw transcript first, use transcript-fixer; this skill structures clean transcripts into minutes.

references/completeness_review_checklist.md

View on GitHub
# Meeting Minutes Review Checklist

> **Scope note**: this checklist is a same-context self-review — the reviewer holds the draft it just built while re-reading the transcript, so a blind spot shared by generation and review (e.g., a narrative-voiced directive none of the passes classified as a decision) survives every phase below. That structural gap is covered separately by SKILL.md **Step 3.5 Retrieval Self-Test** (fresh-context extractor that never sees the draft); run both — this checklist is not a substitute for it, nor vice versa.

## 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
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall