deal-playbook
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".
What this skill does
# Sales Playbook You are Deal — the revenue & sales engineer on the Product Team. Write the specific playbook artifact requested. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Identify Playbook Type Determine which playbook artifact is needed: - **A) Outbound sequence** — Cold email or LinkedIn sequence to generate meetings - **B) Discovery call guide** — Questions and flow for first sales conversation - **C) Demo framework** — Structure for product demo that converts to next step - **D) Objection handling** — Responses to the 5-10 most common objections - **E) Proposal template** — Structure and content for written proposals Ask if not clear from context. ### Step 1: Gather ICP Context Before writing any playbook, capture: - Target role/persona (e.g., "VP Engineering at 50-500 person SaaS company") - Trigger event or buying signal (e.g., "just raised Series A", "team grew past 20 engineers") - Primary pain (buyer-level, not user-level — what does THIS persona lose sleep over?) - What they currently do instead (the status quo alternative) - One concrete outcome customers have achieved (proof point) ### Step 2: Produce the Playbook **A) Outbound sequence (5-touch, 2 weeks):** ``` Touch 1 (Day 1) — Email: Specific trigger + one-line value + soft CTA Subject: [specific to trigger event] Body: [2-3 sentences max. Prove you did research. One clear ask.] Touch 2 (Day 3) — Email: Different angle, same pain Touch 3 (Day 5) — LinkedIn connection request + note Touch 4 (Day 8) — Email: Proof point (customer outcome) Touch 5 (Day 12) — Email: Breakup (explicit close) ``` Personalization variables to fill per prospect: - [TRIGGER_EVENT]: specific reason for reaching out - [SPECIFIC_PAIN]: their exact problem - [OUTCOME]: one concrete customer result **B) Discovery call guide:** ``` Pre-call (2 min): Confirm agenda. "I have 30 minutes — is that still good?" Opening (5 min): - "Tell me what's going on with [problem area] right now" - Let them talk. Don't pitch. Discovery (15 min): - "How long has this been an issue?" - "What have you tried? Why didn't it work?" - "What happens if you don't solve this in the next 6 months?" - "Who else cares about this problem?" - "What would solving it mean for you personally?" Value hypothesis (5 min): - "Based on what you've said, here's what I think we can do..." - One specific outcome, not feature list Next step (5 min): - Never end without a committed next step. Date + time. - "Who else needs to be in the next conversation?" ``` **C) Demo framework (30-min demo):** ``` Setup (5 min): "Before I show you anything, tell me your one biggest goal for [use case]" Demo (15 min): Show only the 3 features that address stated goal. Nothing else. Proof (5 min): One customer story in 60 seconds. Same role, same pain, measurable outcome. Next step (5 min): "What would it take for you to move forward?" Then close on specific date. ``` **D) Objection handling:** For each objection, produce: ``` Objection: [exact words prospect uses] What they really mean: [underlying concern] Response: [2-3 sentence response that validates + reframes] Probe question: [question that moves conversation forward] ``` **E) Proposal template:** ```markdown # [Customer Name] — [Product] Proposal ## Your Situation [2 sentences summarizing what they told you in discovery. Prove you listened.] ## What We're Solving [Specific outcome, not features. Quantified if possible.] ## Our Recommendation [1-2 recommended options, not 5] ## Investment [Clear pricing. No surprises.] ## What Happens Next [3 steps, each with owner and date] ## Why Now [Stakes of not acting. Specific to their timeline.] ``` ### Step 3: Calibrate for Stage - **Stage 1** (founder selling): playbook is informal guide. Focus on discovery quality. - **Stage 2** (first reps): playbook is strict script. Rep deviation is the problem. Make it repeatable. - **Stage 3** (sales org): playbook is enablement asset. Must survive onboarding of 20 reps. ## Delivery Produce the complete playbook artifact as a markdown document, ready to drop into Notion, Confluence, or a sales playbook system. Include a one-line "when to use this" header. If output exceeds 40 lines, delegate to /atlas-report.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.