deal-reviewlisted
Install: claude install-skill stefanoskarakasis/Product-Marketing-Skills
# Deal Review
A review answers three things: is this deal real, what is missing, what changes in the next 14 days. Evidence beats opinion: a claim only the seller made is not proof. It commits to next steps every time, walking away included. It reads your brain and never writes it; what it learns goes to the PMM as proposals.
## Trigger
- **When:** Someone asks about one named open opportunity, a weekly queue, or a new transcript to debrief.
- **Not for:** No opportunity → `prospect-research`. A customer with none open → `customer-context`. A competitor in the deal → `competitive-battlecard`. The committee → `buyer-personas` or `stakeholder-maps`. Writing the follow-up → `writing-assistant`. Call prep, first or open-deal → `discovery-call-prep`. A raw call summary → `interview-summary`.
- **Examples:** "@Claude review the Marlow deal" · "what changed on Marlow since Monday?" (`since`) · "which deals need me this week?" (`queue`)
## Inputs
- **Args:** deal or account; mode `review` (default), `since` (a pasted transcript makes it a debrief), `ask` (one question, thread-sized), `queue`, `mine`. A line starting `log:` records an outcome.
- **Ask, never assume:** deal size, stage, buyer role and typical sales cycle only when missing (read brain Section 2 `sales_cycle` first) and they change the review. One combined question. If unanswered, items that need them read "not assessed".
- **Context keys:** the brain; `/context/deals/`; sibling ledgers read-only (`references/feed-f