sales-meeting-recap

The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.

---
name: sales-meeting-recap
description: Turns raw sales call notes into a structured recap email with agreed next steps - every action item carrying an owner, a date, and a deliverable - plus mutual close plan (mutual action plan) items when the deal warrants one. Restates the buyer's pain in their own words and never invents a commitment the notes don't contain. Covers complex B2B committee deals and transactional or B2C motions. Use whenever the user mentions a recap email, follow-up after a sales call, next steps email, post-call summary, or a mutual action plan, even without the word recap. Do NOT use for judging how the call went (mbfinotti/sales-skills@sales-call-review).
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.3.4"
---

# Meeting Recap

Convert the user's call notes into two artifacts: a recap email the buyer will ratify by replying, and mutual close plan items when the deal is complex enough to warrant a shared plan. The organizing rule is Armand Farrokh's (30MPC): a recap email answers exactly two questions - "Did you make it clear what the prospect needs to do next?" and "Did you remind them why they agreed to take action?" Everything else is decoration, and "nothing should get in the way of what we want them to do."

Second rule: the recap is champion-enablement content. A buying group gives any single vendor only around 5-6% of its purchase time (Gartner 2017 B2B buyer survey), so the email does most of its selling in rooms the rep never enters - write it to be forwarded.

Scope boundaries:

- Work only from notes, transcripts, or descriptions the user supplies.
- Never score or critique how the call was run - that belongs to `mbfinotti/sales-skills@sales-call-review`.
- The post-sale handoff from sales to customer success is out of scope entirely.

## Interview

Ask one question per message; offer multiple-choice options; skip anything the notes or context already answer.

1. Who was on the call - names and roles on both sides? Which buyer contacts should receive the recap?
2. B2B or B2C? Buying committee, or a single decision-maker?
3. Deal stage: first connect, discovery, demo, proposal, or negotiation?
4. Rough deal size and expected cycle length? This sets the recap's weight and whether a close plan pays off.
5. What was actually agreed on the call - commitments, owners, dates, exactly as stated?
6. Is the next meeting booked with a calendar invite? If not, was a specific date discussed?
7. Does a mutual close plan already exist for this deal, or should this call seed one?
8. By when must the recap land - within the hour, today, or is tomorrow acceptable? A same-hour answer promotes the short recap and deletes anything needing a working session.
9. One-off win or compounding asset: this deal's follow-up only, or a pattern repeated across the pipeline? Compounding promotes the close plan and the automated sequence; one-off promotes the hand-written recap alone.
10. Effort ceiling: how many minutes per recap, across how many live deals? A tight ceiling deletes the full mutual action plan and caps the recap at one screen.

Every ordering below is a default, not a law - it shifts with the deal, with the pipeline, and with who executes it. Re-rank each one against these answers and against what you already know about the user: a rep running dozens of small deals, a single strategic pursuit, and a CRM that already auto-drafts recaps each invert a different ordering. Delete the options their constraints rule out rather than parking them at the bottom, where they quietly reappear as scope.

## Anti-fabrication rule

The load-bearing guard. A recap containing a commitment the buyer never made destroys the shared record it exists to create.

- Never invent a commitment, owner, date, quote, attendee, or decision the notes do not contain.
- Treat a gap as output, not as something to fill: list missing owners, dates, and unconfirmed items in an "Open gaps" block and ask the user.
- Mark any step