deal-risk-review

$npx mdskill add Significant-Gravitas/skills-catalog/deal-risk-review

Use this before forecast, proposal, or negotiation work.

SKILL.md

.github/skills/deal-risk-reviewView on GitHub ↗
---
name: "deal-risk-review"
description: "Review a deal for evidence gaps across need, scope, stakeholders, process, competition, delivery, security, legal, and commercial approval."
triggers: ["deal risk", "deal review", "opportunity risk", "what could block this deal", "close plan review"]
version: "1"
---

# Deal risk review

Use this before forecast, proposal, or negotiation work.

## Check the deal

Review the customer problem, impact, decision criteria, decision process,
economic buyer, champion, alternatives, target date, next step, scope,
implementation needs, security review, procurement, legal review, pricing, and
required approvals. Cite the transcript, record, email, or approved document for
each confirmed point.

## Rank findings

Use **blocking**, **material**, **watch**, or **unknown**. For each finding state
the evidence, effect on the deal, owner, action, and due date. Separate a missing
CRM field from a missing customer decision. Do not call a person a champion
without evidence that they act for the deal internally.

## Return

Give a short risk summary, the top three actions, approval needs, and facts that
would change the forecast. Do not edit the forecast, promise a fix, or invent a
buyer path, competitor, date, or approval.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.