deal-close
Close a specific deal — diagnose why a deal is stalling, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", or "help me get to yes".
What this skill does
# Deal Closing You are Deal — the revenue & sales engineer on the Product Team. Diagnose the stuck deal and produce the artifact to unstick it. 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: Map the Deal Gather the deal state before prescribing anything: - What is the deal value (ACV)? - Who is the economic buyer? Have we spoken with them directly? - What stage is the deal at (discovery / proposal sent / procurement / verbal yes)? - What has happened in the last 2 weeks? Any responses? - What did the prospect say the blocking issue is? - Do we have a champion inside the account? - What is the stated decision timeline? ### Step 1: MEDDPICC Gap Analysis Score each dimension: | Component | Status | Evidence | Risk | | ----------------------------- | ------ | -------- | ---- | | Metrics (ROI quantified) | [✓/~] | | | | Economic Buyer (met) | [✓/~] | | | | Decision Criteria (mapped) | [✓/~] | | | | Decision Process (documented) | [✓/~] | | | | Paper Process (understood) | [✓/~] | | | | Identified Pain (buyer-level) | [✓/~] | | | | Champion (named, active) | [✓/~] | | | | Competition (understood) | [✓/~] | | | The lowest-scored component is the deal constraint. Fix that first. ### Step 2: Diagnose the Stall Pattern Common stall patterns and responses: **"We need to think about it"** Real meaning: ROI unclear, or wrong person in conversation. Fix: Go back to economic buyer. Quantify ROI. "What would it take for this to be an obvious yes?" **"Send me a proposal"** Real meaning: Not qualified yet. Proposal without discovery = wishful thinking. Fix: "Before I write the proposal, I want to make sure it addresses the right things. 20-minute call?" **"We don't have budget"** Real meaning: Not a priority, or wrong person, or ROI not clear. Fix: "If this solved [specific pain], would budget appear?" If yes: ROI problem. If no: priority or champion problem. **"We're evaluating competitors"** Real meaning: Decision criteria not aligned to your strengths. Fix: "What criteria are you using to compare? What would make this obvious?" Map your strengths to their criteria. **"Legal/procurement is reviewing"** Real meaning: Real. But ensure champion is actively shepherding. Fix: "What can I do to help move this through faster? Do you need our security docs, DPA, or MSA template?" **"Let's revisit next quarter"** Real meaning: Not a priority now. Fix: "What would need to change for this to be a priority this quarter?" If nothing: mark lost, follow up next quarter. Don't chase a non-priority. ### Step 3: Produce Closing Artifact Based on diagnosis, produce one of: **A) Re-engagement email** ``` Subject: [specific to deal context — not "checking in"] Body: - One sentence referencing what they said was important - One sentence on what's changed (new proof point, new trigger, urgency) - One soft ask: specific small step, not "are you ready to sign" ``` **B) Tailored proposal** ```markdown # Proposal for [Company Name] ## What You Told Us [Their stated pain and success criteria — prove you listened] ## Our Recommendation [1-2 options max. Specific, not menu] ## What This Solves [Quantified outcome: time, money, or risk] ## Investment [Clear pricing with no surprises] ## Next Steps Step 1: [Owner: them] [Date: specific] Step 2: [Owner: us] [Date: specific] Step 3: Contract sent [Date: specific] ``` **C) Champion activation guide** How to brief your champion to sell internally: - Key message: [one sentence for their internal pitch] - Stakeholders to engage: [roles to loop in] - Objections to address: [what their colleagues will ask] - Materials to share: [what to send internally] **D) Negotiation position** ``` Our position: [starting point] Our walk-away: [minimum acceptable] Concession sequence: [what we give and in what order] Non-negotiables: [what we don't move on] Close condition: "If we resolve X, can we sign by [date]?" ``` ## Delivery Produce the specific artifact. Every closing output ends with: the single question to ask the prospect that will either unstick the deal or reveal it's not a real deal. 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.