pm-meeting
Structured meeting notes, decisions log, and action items from raw notes or a transcript
/pm-meeting▊When to use
After any meeting where notes or a transcript exist. Detects meeting type from content and applies the correct summary template automatically.
What it produces
- Structured meeting summary - template varies by meeting type
- Decisions log - what was settled in this session (should not be re-opened without new evidence)
- Action items - each tagged with destination and owner
- Notion push - new record in Meetings DB + linked tasks (if Notion URL configured in
pureinn-variables.md)
How to invoke
/pm-meeting # interactive - paste notes/transcript or reference a file
/pm-meeting --agent # autonomous synthesis from notes file
Input can be:
- Pasted notes or transcript - used directly
- File or folder reference - read in full (deep ingestion, all files recursively)
- No notes - guided recall: 3-4 targeted questions (what was the meeting about, who attended, what was decided, what needs to happen next); output marked as reconstructed from recall
Seven meeting types
The skill detects type from the content. Each type has its own summary template and routing:
| Type | Detection keywords | Primary routing |
|---|---|---|
| Customer Discovery | customer, user, prospect, "they said", pain, interview | Insights → personas / jtbd / pm-problem-validation |
| Client / Requirements Discovery | client, brief, requirements, "they want", budget, "like [company]", scope, quote, proposal | Discovery Report / Scope Brief / personas [CLIENT-ASSERTED] |
| Product Review | FEAT-, AC-, spec, design review, Section, Figma | Feature Card update / pm-feature-design re-run |
| Planning / Grooming | sprint, stripe, priority, backlog, phase, who takes what | feature_list update / pm-stripe / pm-mvp-scope |
| Strategic Review | roadmap, investor, revenue, phase gate, business model, PRD | pm-prd / pm-product-roadmap delta |
| Standup / Retro | yesterday, today, blocker, retrospective, what went well | pm-stripe (blockers) / Notion tasks (retro actions) |
| Partner / Vendor | partner, vendor, contract, integration, API, SLA | Notion tasks + follow-up calendar |
Client Discovery captures findings from whoever commissioned the build - requirements, references classified directive/hypothesis (with explicit non-goals), budget/decision process, and process/exception findings tagged [CANDIDATE-BR]. Distinct from Customer Discovery (end users). See pm-discovery-interview for the full question set used to run these sessions.
Action item tags
Every action item gets a destination tag regardless of meeting type:
| Tag | Meaning |
|---|---|
[Notion Task] | Standalone task in Notion, assigned with deadline |
[Feature Card: FEAT-ID] | Update or create a Feature Card |
[Meeting: person, topic, by when] | Schedule a follow-up meeting |
[Skill: /pm-xxx] | Run a framework skill to process this item |
Dependencies
Recommended:
pm-team-roster- to resolve names to real team members when assigning action itemspm-comms-charter- defines the meeting rhythm;pm-meetingcaptures each individual instancepureinn-variables.md-Meetingskey must contain the Notion DB URL for push
Produces for:
- Notion Meetings DB (if configured)
- Feature Cards (for Product Review and Planning types)
- Downstream skills depending on meeting type (see routing table above)
Related skills: pm-personas, jtbd-building, pm-problem-validation, pm-stripe, pm-feature-card, pm-product-roadmap, pm-team-roster, pm-discovery-interview, pm-discovery-report, pm-scope-brief