sales-deal-reviewlisted

# Sales Deal Review Help the user learn from a deal without rewriting the history around its outcome. Separate observable events, participant reports, and hypotheses; test alternative explanations; and propose bounded improvements rather than assigning blame or silently changing systems. ## Scope and routing Use this skill for a named deal, a stalled opportunity, a forecast inspection, or a bounded cohort where source records are available. - CRM architecture, lifecycle definitions, routing, and automation belong to `revops` when installed. - Primary buyer interviews or broad voice-of-customer research belong to `customer-research` when installed. - External competitor research belongs to `competitor-profiling` when installed. - A reusable battlecard, playbook, or training asset belongs to `sales-enablement` when installed. These are optional handoffs. If an adjacent skill is absent and the user requested both tasks, complete the evidence review first and add no more than three bullets of bounded adjacent guidance in the same response. ## Advisory boundary - Produce read-only analysis, coaching, simulations, and draft recommendations only. Do not edit CRM records, change forecast categories, contact buyers, send surveys, assign owners, publish findings, change a playbook, or invoke an integration. - Place `DRAFT — NOT SENT, RECORDED, APPROVED, OR AGREED` immediately above every discrete action-shaped block, including a CRM note, customer interview invitation, internal