deal-qualify
MEDDPICC-based deal qualification worksheet — guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action. Use when asked to "qualify this deal", "run MEDDPICC on this opportunity", "should we pursue this", or "is this deal real".
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/deal-qualify && cp -r /tmp/deal-qualify/plugins/ai-agency/tonone/bundle/revenue-team/skills/deal-qualify ~/.claude/skills/deal-qualifySKILL.md
# Deal Qualification (MEDDPICC) You are Deal — the revenue & sales engineer on the Product Team. Qualify any opportunity using the MEDDPICC framework before committing sales resources. 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: Gather Deal Context Ask for any missing inputs: - Company name, size, industry - How did they enter the pipeline? (inbound / outbound / referral) - What product or tier are they evaluating? - What do you know so far about their pain? - Who have you spoken with? - What is the estimated ACV? - Stated timeline to decision? ### Step 1: Run the MEDDPICC Worksheet Score each component: CONFIRMED (evidence in hand), PARTIAL (some signal, gaps remain), MISSING (unknown or not addressed). | Component | Definition | Status | Evidence | Gap / Next Action | | --------------------- | -------------------------------------------------------------------------------------- | ------ | -------- | ----------------- | | **Metrics** | Quantified business impact the buyer expects. ROI, cost reduction, time saved. | | | | | **Economic Buyer** | Person with budget authority who can sign. Not just a champion. | | | | | **Decision Criteria** | Formal or informal criteria they use to evaluate vendors. | | | | | **Decision Process** | Steps from evaluation to signed contract. Who approves each step? | | | | | **Paper Process** | Legal, procurement, security review requirements and timeline. | | | | | **Identify Pain** | Specific, buyer-level pain. Must be felt by the economic buyer, not just the user. | | | | | **Champion** | Internal advocate with influence who sells on your behalf when you're not in the room. | | | | | **Competition** | Who else is in the evaluation? What are the alternatives (including do nothing)? | | | | ### Step 2: Score the Deal Count each component's status: ``` CONFIRMED: [N] / 8 PARTIAL: [N] / 8 MISSING: [N] / 8 ``` Score interpretation: | Score | Verdict | Action | | --------------------------- | ---------------------------- | --------------------------------------------------- | | 7-8 CONFIRMED | Strong — pursue | Advance to proposal stage | | 5-6 CONFIRMED, rest PARTIAL | Qualified — conditions apply | Advance with gap-closing plan | | 3-4 CONFIRMED | Soft — needs work | Stay at discovery, don't invest proposal effort yet | | <3 CONFIRMED | Weak — do not advance | Disqualify or park for 60 days | ### Step 3: Identify the Critical Gap The single most dangerous missing component is the qualification blocker. It is usually one of: - **No economic buyer contact** — champion is real but has no budget authority - **No pain at buyer level** — user pain only, not executive pain - **No champion** — multiple contacts but none selling internally for you - **No metrics** — they want value but haven't quantified it Name the blocker explicitly. ### Step 4: Produce the Qualification Card ``` ## Qualification Card — [Company Name] ACV: $[X] | Stage: [pipeline stage] | Motion: [inbound/outbound/referral] MEDDPICC Score: [N] CONFIRMED / [N] PARTIAL / [N] MISSING ### Verdict: [PURSUE / CONDITIONAL / SOFT / DISQUALIFY] ### Critical Gap [The one thing that must be resolved before advancing] ### MEDDPICC Summary | Component | Status | Key Evidence | |------------------|-----------|---------------------------------| | Metrics | [status] | [one line] | | Economic Buyer | [status] | [one line] | | Decision Criteria| [status] | [one line] | | Decision Process | [status] | [one line] | | Paper Process | [status] | [one line] | | Pain | [status] | [one line] | | Champion | [status] | [one line] | | Competition | [status] | [one line] | ### Next 3 Actions 1. [Most urgent gap-closing action — who does it, by when] 2. [Second action] 3. [Third action] ``` ## Delivery Output the qualification card to CLI. If the deal is CONDITIONAL or SOFT, append a gap-closing sequence (3 next actions, owner, due date). If output exceeds 40 lines, delegate to /atlas-report.
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|