meeting-prep

Name: meeting-prep
Author: etrebels

17stars1forks

How to install meeting-prep?

etrebels/claude-code-growth-os/meeting-prep

$npx -y skills add etrebels/claude-code-growth-os --skill meeting-prep

Installs into the current project.

Summary

Build a pre-meeting briefing — who's in the room, what they care about, your goal, and the questions to ask. Trigger when the user asks to prep for a meeting or call, "what should I know before", or names an upcoming meeting.

Files · 1

View on GitHub

SKILL.md

1	# Meeting Prep (pre-meeting briefing)
2
3	Before a meeting, build a one-screen brief:
4
5	1. Who's in the room and what each likely cares about.
6	2. Where this sits — pull from `ops/pipeline.md` and any prior notes: last contact, open threads, commitments outstanding.
7	3. Your one goal for the meeting, and the single decision you want out of it.
8	4. The questions to ask — labels + calibrated questions (see below).
9	5. The one risk or objection to be ready for — name it first, before they raise it.
10
11	Pull context from `ops/` and the relevant meeting notes; don't invent attendees or history you weren't given.
12
13	## Asking the right kind of questions (Chris Voss, Never Split the Difference)
14
15	The questions decide the meeting. Two moves do most of the work:
16
17	- Label, then ask. Name the thing they're likely feeling before you question it: "It seems like…" / "It sounds like…" Then stop talking and let them respond. A label lowers the guard; the silence pulls out the real answer.
18	- Calibrated questions start with What or How — never "why" (which sounds like an accusation), never yes/no (which closes things down). They make the other person do the thinking and hand you the information.
19
20	Load 3–5 calibrated questions for the meeting. A reusable set:
21
22	- "What's the hardest part of that for your team right now?"
23	- "How does that show up in your week?"
24	- "What have you already tried that didn't work the way you hoped?"
25	- "What does that cost you today?" (time, rework, decisions made on partial information)
26	- "How would you know this had been solved?"
27	- "How does a decision like this usually get made on your side?" — surfaces the real process and who else matters
28	- "What would need to be true for this to be worth doing?"
29
30	Close two ways:
31	- A summary they confirm — play their situation back so well they say "that's right." (Not "you're right," which usually means let's wrap up.)
32	- The one question that surfaces the hidden thing: "Is there anything I should know that I haven't asked about?"
33
34	Replace on sight: "Why are you still using X?" → "What's kept X in place?" · "Do you have a process for X?" → "How do you handle X today?" · "Is that a problem?" → "What does that cost you?" · "Would you agree that…?" → delete it.
35
36	## Depth
37	- quick: the goal + one label + three calibrated questions.
38	- standard: the full brief above, with the label + 3–5 calibrated questions and a summary-to-confirm.
39	- deep: + a likely-objections list (named first, before they raise them), a fallback ask if the main one stalls, and the hidden-thing question to close.

People who liked this also viewed

6 picks

Type

meeting-prep

17stars1forks

View on GitHub

How to install meeting-prep?

etrebels/claude-code-growth-os/meeting-prep

$npx -y skills add etrebels/claude-code-growth-os --skill meeting-prep

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Meeting Prep (pre-meeting briefing)
2
3	Before a meeting, build a one-screen brief:
4
5	1. Who's in the room and what each likely cares about.
6	2. Where this sits — pull from `ops/pipeline.md` and any prior notes: last contact, open threads, commitments outstanding.
7	3. Your one goal for the meeting, and the single decision you want out of it.
8	4. The questions to ask — labels + calibrated questions (see below).
9	5. The one risk or objection to be ready for — name it first, before they raise it.
10
11	Pull context from `ops/` and the relevant meeting notes; don't invent attendees or history you weren't given.
12
13	## Asking the right kind of questions (Chris Voss, Never Split the Difference)
14
15	The questions decide the meeting. Two moves do most of the work:
16
17	- Label, then ask. Name the thing they're likely feeling before you question it: "It seems like…" / "It sounds like…" Then stop talking and let them respond. A label lowers the guard; the silence pulls out the real answer.
18	- Calibrated questions start with What or How — never "why" (which sounds like an accusation), never yes/no (which closes things down). They make the other person do the thinking and hand you the information.
19
20	Load 3–5 calibrated questions for the meeting. A reusable set:
21
22	- "What's the hardest part of that for your team right now?"
23	- "How does that show up in your week?"
24	- "What have you already tried that didn't work the way you hoped?"
25	- "What does that cost you today?" (time, rework, decisions made on partial information)
26	- "How would you know this had been solved?"
27	- "How does a decision like this usually get made on your side?" — surfaces the real process and who else matters
28	- "What would need to be true for this to be worth doing?"
29
30	Close two ways:
31	- A summary they confirm — play their situation back so well they say "that's right." (Not "you're right," which usually means let's wrap up.)
32	- The one question that surfaces the hidden thing: "Is there anything I should know that I haven't asked about?"
33
34	Replace on sight: "Why are you still using X?" → "What's kept X in place?" · "Do you have a process for X?" → "How do you handle X today?" · "Is that a problem?" → "What does that cost you?" · "Would you agree that…?" → delete it.
35
36	## Depth
37	- quick: the goal + one label + three calibrated questions.
38	- standard: the full brief above, with the label + 3–5 calibrated questions and a summary-to-confirm.
39	- deep: + a likely-objections list (named first, before they raise them), a fallback ask if the main one stalls, and the hidden-thing question to close.

People who liked this also viewed

6 picks

Type