Generates framework-based talking points and discussion guides tailored to meeting type. Activates for talking point requests, discussion guides, meeting agendas, or 'what should I bring up in this meeting?' Selects from SPIN, GROW, SBI, and other frameworks based on meeting classification, with 'Do NOT Mention' guardrails and context-aware customization.
From founder-osnpx claudepluginhub thecloudtips/founder-os --plugin founder-osThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Generate structured, framework-based talking points and discussion guides for meetings. Select the appropriate conversational framework based on meeting type, produce 3-5 actionable talking points per meeting, build an opener and close structure, and customize output based on CRM deal stage, relationship status, and pending items. Consume meeting context data (attendee profiles, open items, recent communications) produced upstream in the pipeline and transform it into a ready-to-use discussion guide.
Map every meeting to exactly one framework. Use the meeting type classification from the meeting-context skill as input. Never blend frameworks -- pick one and apply it consistently.
| Meeting Type | Framework | Core Structure |
|---|---|---|
| external-client | SPIN | Situation, Problem, Implication, Need-payoff |
| one-on-one | GROW | Goal, Reality, Options, Way-forward |
| internal-sync | SBI | Situation, Behavior, Impact |
| ad-hoc | Context-Gathering | Open questions to establish purpose and alignment |
| recurring | Delta-Based Agenda | What changed, what is blocked, what is next |
| group-meeting | Contribution Mapping | Who owns what, expected inputs, decision points |
When a meeting could match multiple types, defer to the type already classified upstream. Do not reclassify.
Structure talking points to guide client conversations from discovery through actionable outcomes.
Situation -- Establish shared context. Reference known facts: active deals, project milestones, contract status, last interaction. Frame as confirmation questions, not assumptions. Example: "Confirm the current timeline for the Q2 launch -- last discussed on [date]."
Problem -- Surface pain points or blockers. Reference open items, overdue deliverables, or flagged risks. Frame as open-ended questions. Example: "Ask what the biggest blocker is for [deliverable] this week."
Implication -- Quantify the cost of inaction. Connect problems to business impact using deal value, timeline data, or risk flags. Example: "If the [deliverable] delay extends past [date], how does that affect [downstream milestone]?"
Need-payoff -- Propose solutions and next steps. Lead with actions the user can offer, not demands of the client. Example: "Propose accelerating the review cycle to recover 1 week on the timeline."
Structure talking points to facilitate coaching or alignment conversations.
Goal -- Define the meeting's purpose. Reference the attendee's objectives, project assignments, or previously stated goals. Example: "Check in on progress toward the [quarterly goal] discussed on [date]."
Reality -- Assess current state honestly. Surface task completion rates, blockers, feedback received, and items from the last one-on-one. Example: "Review the 3 action items from the last 1:1 -- which are complete, which are blocked?"
Options -- Explore 2-3 alternative approaches to current challenges. Frame as collaborative brainstorming, not directives. Example: "Consider whether to prioritize [task A] over [task B] given current constraints."
Way-forward -- Commit to specific next steps with owners and deadlines. Every one-on-one must end with at least one concrete commitment from each participant. Example: "Agree on 2 deliverables for next week and set check-in dates."
Structure talking points around observable situations and their impact.
Situation -- State the specific context: sprint, project phase, deadline, or event. Be concrete about time and scope. Example: "We are 3 days from the [milestone] deadline with 4 open items remaining."
Behavior -- Describe observable actions or outcomes without judgment language. Reference shipped features, completed tasks, or missed deadlines. Example: "The API integration shipped Tuesday and handles [N] requests/day."
Impact -- Connect behavior to team or project outcomes. Quantify downstream effects, velocity changes, or risk exposure. Example: "The early delivery unblocked the frontend team -- integration started 2 days ahead of plan."
Generate 3-5 open-ended questions in this order:
When attendee context is available from CRM or email, weave it into the questions -- do not ask for information already known.
Generate talking points in three categories:
Scan notes from the previous occurrence. Carry unresolved items forward. Flag items appearing in 3+ consecutive occurrences as "stale recurring" and recommend resolution or removal.
Generate a contribution map for meetings with 4+ attendees:
Generate a "Do NOT mention" list when any of these conditions are detected:
Place the list after talking points, clearly separated with a warning label. Omit the section entirely when no items apply.
Generate a 1-2 sentence opener tailored to meeting type:
| Meeting Type | Opener Pattern |
|---|---|
| external-client | Acknowledge the client's time, reference a recent milestone, state the objective. |
| one-on-one | Genuine check-in question, then transition to first agenda item. |
| internal-sync | State the time box and 2-3 items to cover, invite additions. |
| ad-hoc | State your understanding of the purpose, ask for confirmation. |
| recurring | Summarize the top delta since last meeting in one sentence, transition to agenda. |
| group-meeting | State the objective and expected output, walk through the agenda. |
When relationship status is Dormant or Cooling, open with fresh value (insight, resource, offer) rather than a backward-looking reference.
Generate 2-3 concrete next steps for the meeting's close. Each must include:
Generate a 1-sentence close that summarizes the key outcome and confirms the next interaction (meeting date, follow-up email, or deliverable deadline).
Apply all applicable adjustments -- they stack.
| Deal Stage | Adjustment |
|---|---|
| Lead / Qualified | Focus on discovery and needs assessment. Ask more than you propose. |
| Proposal | Focus on differentiators and value quantification. Reference proposal elements. |
| Negotiation | Focus on terms, timeline, mutual commitments. Avoid introducing new scope. |
| Closed Won | Focus on kickoff logistics, onboarding, expectation setting. |
| Closed Lost | Post-mortem only. Focus on lessons learned and future opportunities. |
| Status | Adjustment |
|---|---|
| Active (<30 days) | Reference recent interactions. Build continuity: "Following up on our [last interaction]..." |
| Cooling (30-90 days) | Re-establish rapport first. Lead with value. Do NOT reference the time gap. |
| Dormant (>90 days) | Treat as near-fresh. Provide context on who you are. Bring a specific reconnection reason. |
## Discussion Guide: [Meeting Title]
**Framework**: [Framework Name] ([Meeting Type])
**Date**: [meeting date and time]
**Attendees**: [comma-separated names]
### Opener
[1-2 sentence suggested opener]
### Talking Points
1. **[Action verb] [topic]** -- [1-2 sentence context and rationale]
2. **[Action verb] [topic]** -- [1-2 sentence context and rationale]
3. **[Action verb] [topic]** -- [1-2 sentence context and rationale]
### Do NOT Mention
> The following topics should be avoided in this meeting:
> - [Item with rationale]
> - [Item with rationale]
### Proposed Next Steps
- [ ] [Action] -- Owner: [name] -- By: [date]
- [ ] [Action] -- Owner: [name] -- By: [date]
### Close
[1-sentence summary and next interaction confirmation]
When upstream data is minimal (no CRM match, no email history, no notes), fall back to the context-gathering framework regardless of detected meeting type. Note in output: "Limited context available -- discussion guide uses context-gathering questions."
When CRM indicates a healthy relationship but emails show frustration or escalation language, prioritize the negative signal. Lead with a talking point that addresses the concern. Add a "Do NOT mention" item for positive metrics that could seem dismissive.
Reduce talking points to exactly 2. Drop "Do NOT mention" unless a critical item applies. Compress the opener to one sentence.
When 50%+ of attendees have no CRM or email context, switch to contribution-mapping regardless of original type. Focus on establishing who is present and what they need.
Treat as ad-hoc for talking point purposes. Generate context-gathering questions alongside the delta structure. Recommend establishing a shared notes document.
Do not repeat the same items. Assign each item to the more appropriate meeting context and reference the other: "Defer [topic] to the [next meeting title] discussion."