discovery-prep
Use this skill when a specific meeting with a named person is on the calendar and nobody has done the homework - "I have a call in an hour", "who are these people", "build me a brief for tomorrow's call", "what do I ask them", "a new stakeholder joined the thread, what do I need to know", "prep me for the renewal", "what are they going to push back on", "we are re-engaging a stale deal, what changed at their company", "brief me before the demo". Reads the CRM record, the prior thread, public sources and recent signals, then produces a one-page brief a rep scans in five minutes: company and person snapshot, three pain hypotheses with the evidence behind each, an opener, the questions to ask, the objections to expect with responses, and the next step to propose. The brief is internal, and this skill never contacts the prospect. NOT scoring a list of accounts for fit, which is the icp-modeller skill and runs long before anybody books a meeting. NOT the outbound message that gets the meeti
Workflowsio · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Workflowsio/company-os-starter-kit --skill discovery-prepAbout this skill
name: discovery-prep description: | Use this skill when a specific meeting with a named person is on the calendar and nobody has done the homework - "I have a call in an hour", "who are these people", "build me a brief for tomorrow's call", "what do I ask them", "a new stakeholder joined the thread, what do I need to know", "prep me for the renewal", "what are they going to push back on", "we are re-engaging a stale deal, what changed at their company", "brief me before the demo". Reads the CRM record, the prior thread, public sources and recent signals, then produces a one-page brief a rep scans in five minutes: company and person snapshot, three pain hypotheses with the evidence behind each, an opener, the questions to ask, the objections to expect with responses, and the next step to propose. The brief is internal, and this skill never contacts the prospect. NOT scoring a list of accounts for fit, which is the icp-modeller skill and runs long before anybody books a meeting. NOT the outbound message that gets the meeting booked in the first place, which is outbound-copywriter.
Discovery prep
When this applies
One named person, one scheduled conversation, and fifteen minutes or less to get ready. It covers a first call, a follow-up where new stakeholders are joining, a demo, a negotiation, a renewal or expansion conversation, and the refresh before reaching back into a stale opportunity.
Maturity: the research layers, the call-type playbooks and the objection responses have been used in real sales conversations. The objection table is the part that improves fastest once you start adding your own, so treat the shipped rows as a starting library rather than the finished one.
What it produces
One page, in this order, because that is the order a rep reads it in with four minutes to go:
- A 30-second version that stands alone if nothing else gets read.
- Company snapshot and person profile.
- Three pain hypotheses, each with the evidence behind it, clearly marked as hypotheses.
- An opener referencing something specific to them, and the bridge from rapport into discovery.
- The questions, grouped into discovery, qualification and closing.
- The objections to expect, with a response for each.
- The next step to propose, with who, what and when.
Fill these in
{{CRM}}- where prior activity, notes and deal history live{{ENRICHMENT}}- what supplies company and person data, and what a lookup costs{{WHAT_WE_SELL}}- one sentence, so pain hypotheses and value framing are tailored rather than generic{{PROOF_POINTS}}- the customer results that can be cited, and which names are cleared for use{{PREP_BUDGET}}- default minutes of prep for a standard call (default: 10) and for a high-value one (default: 30)
First run: the customization interview
Run this as a one-time setup step, outside any live engagement, and never mid-run. It edits files, and editing a skill or its reference material while it is being used against real work is how a run half-follows two versions of its own instructions. Company-level answers belong in these files; anything specific to one account or one person belongs in clients/<slug>/ or company-wiki/, not in a reference file every account's run reads.
Read before you ask. Pull three recent closed-won and closed-lost records from {{CRM}} and look at what actually appears in the notes, because that tells you which questions this team already asks well and which ones they never get to. Present that, then ask what the records cannot answer.
- What do you sell, in one sentence a buyer would recognise?
- Which proof points can be cited by name, and which have to stay anonymous?
- What are the three objections you hear most, and what currently works against each?
- Who are you usually compared against, and what is your honest differentiator against each?
- What is your standard next step after a first call?
- What is off limits to mention: a competitor's legal trouble, a customer under NDA, anything else.
Write the answers into references/briefing-template.md under objections and competitive positioning, and the placeholders into this file. The objection library is the part of this skill that compounds, so every new objection heard on a live call gets added with the response that worked.
Reference routing
| File | What it contains | When to read it | What breaks if you skip it |
|---|---|---|---|
references/research-layers.md | The four research layers with every data point, where it comes from and why it matters, plus the source quick reference | At step 2, while researching | You research the company and not the person, which is the most common way a brief still produces a generic call |
references/call-type-playbooks.md | Five call types with the goal, the prep emphasis, the time structure, the key questions, what not to do, and the success measure | At step 1, before any research, because the call type decides which layers matter | You bring first-call prep to a negotiation and spend the meeting re-discovering things they already told you |
references/briefing-template.md | The full one-page template, the objection table with responses, competitive positioning and the do-not-say list | At step 4, while assembling, and at step 5 before handing it over | The brief becomes research notes rather than something usable in the four minutes before a call |
Step 1 - Identify the call type first
Everything downstream depends on this. A first call and a renewal need different research, different questions and a different structure, and the same prep given to both is wrong for at least one.
Ask, or infer from {{CRM}} and say what you inferred: first call, follow-up, demo, negotiation, or renewal and expansion. Then read the matching playbook.
Step 2 - Research in layers, bounded by the time available
Four layers, each adding depth. Do not run all four by reflex.
- 10 minutes: lay