arrows-agentic-playbook-builder

Most teams don't have a sales playbook they trust: it's in the heads of the best reps, or in a document nobody opens. This skill reads the whole pipeline in depth (deals, calls, email, docs) and writes down how the team actually runs its sales process, so anyone who reads it understands how deals should be run: the leadership team, a rep hired next month, a consultant or agency, and any AI assistant the team uses.

It's two things in one: the basics of the business (what we sell, why customers buy, who we sell to and who we don't) and an SOP of plays: what the team does at each moment ("when a demo is booked", "after the first call") and in each situation (the kinds of buyers and companies that show up in their deals, a competitor coming up, a deal going quiet). Every play uses the same card:

When:        the trigger, checkable on a real deal
Who it's for: the kind of buyer or company, or every deal
Goal:        what this play is for
Steps:       in order, each with an owner and timing
What we say: a line or question from the team's own winning calls and emails
Hand off when: when to bring in a manager, specialist or someone else
Done when:   what you can see on the deal
Seen in:     how often the team's winning deals did this

The plays come from what the team's winning deals actually did, not from generic sales advice. Where the team has no consistent way of handling a moment yet, the playbook says so as a gap to decide, never an invented play.

What	Who it's for	What's in it
The playbook page	Anyone: the team, a new hire, a manager, a consultant	One visual page, the same layout every time: what we sell and why, who we sell to, how we sell at a glance, the plays at a glance, plays by who books, moment by moment, when things happen, pricing and closing, handoffs, how we run the team, what we say, working with AI, gaps to decide
arrows-sales-playbook.md	People, and any AI assistant that reads it	The same playbook as a file to load into any AI tool (a Claude project, a ChatGPT project or custom GPT, a Gemini Gem, a Copilot agent), so it helps with every deal the team's way

It also refreshes the team files setup made (arrows-sales-process.md, arrows-buyers-and-competitors.md) so every Sales Skill works from the same facts. Setup stays the quick start for every rep; this is the deep version of the team's process, usually run by the leader.

Starting point	What you get
No playbook (or "it's in my head")	The page and the playbook file, built from the team's deals, calls, email and docs
A playbook already	Every rule in it counted against real deals ("multithread by the demo: 7 of 24"), and the page and file updated, keeping what still holds

This is the deepest Sales Skill: expect 20–40 minutes of reading, with progress shown as it goes. The person replies twice: once at the start, once to confirm what you found.

Step 1: Find what exists, and ask once

Read the profile files first; they're a head start, not the answer:

• arrows-sales-process.md: ## Why we win and lose, ## Pipeline stages, ## Discovery and qualification, ## Numbers, ## Open questions.
• arrows-buyers-and-competitors.md: ## What we sell and who we sell to, ## Pricing and packaging, ## Competitors.
• arrows-how-i-work.md: ## About me (rep, leader or both), ## What I do on my best deals, ## What slips.
• arrows-how-we-work.md (leaders): ## Our team, ## Every rep, every deal, ## What I want to see weekly.
• arrows-crm-guide.md (if present): ## How deals move, ## Required by stage, ## Stage evidence, ## What to update, when.
• arrows-sales-playbook.md: built by this skill before. If present and they didn't ask to refresh, offer to refresh, or to check deals against it (Step 2's playbook check, then go straight to the results).

Search connected documents (Google Drive, Notion, Confluence, SharePoint, shared folders) for an existing playbook and its relatives: "playbook", "sales process", "stage definitions", "exit criteria", "qualification", "MEDDIC"/"MEDDPICC"/"SPICED"/"BANT", "discovery questions", "battlecard", "objection", "mutual action plan"/"close plan", "onboarding", "enablement", "talk track", "pitch deck". Note each title, link and last-edited date.