← ClaudeAtlas

roadmap-reality-checklisted

Strategy-stage skill: audits a roadmap against unit economics — every item tagged supported or unsupported with the economic mechanism stated. Use when the user provides a roadmap plus business numbers and asks what's economically justified — 'reality-check this roadmap', 'which items pay for themselves', 'what survives contact with the P&L', 'does this lineup make economic sense' — or when /pm routes such a request here. Do NOT use to author a roadmap, to prioritize purely by customer impact without economics, to size markets (opportunity-sizer's job), or for definitions of unit-economics terms.
Abhillashjadhav/PM-agent-OS · ★ 1 · AI & Automation · score 60
Install: claude install-skill Abhillashjadhav/PM-agent-OS
# Roadmap Reality Check A roadmap in, an economics audit out. Every item must show its causal chain to money — or wear the UNSUPPORTED tag until it can. ## Verification gates (defined first; output is blocked until all pass) - **G1 — Tag + mechanism:** every roadmap item is tagged `SUPPORTED` or `UNSUPPORTED (as stated)`, and every tag carries a stated economic mechanism — the causal chain to revenue, gross margin, retention, or CAC, quantified from provided numbers where possible. A tag without a mechanism fails. - **G2 — Input-only arithmetic:** all math uses numbers from the input; anything else is `[ESTIMATE: derivation]`. Imported industry benchmarks ("PLG converts at 3%") presented as fact fail the gate. - **G3 — Flip conditions:** every UNSUPPORTED item names the missing evidence or number that would flip it. UNSUPPORTED is a verdict on the stated case, not a kill order — the output must say so. ## Steps 1. **Bank the numbers.** Extract price, margin, CAC, churn, user count, and any per-item figures from the input. These are the only facts. Missing a number the audit needs? Say which, and either ask or proceed with a labeled ESTIMATE range. 2. **Trace each item's mechanism.** Which lever does it pull — new revenue (deals, expansion), margin (COGS, support cost), retention (churn), or acquisition (CAC, conversion)? Write the chain: R4 → fewer settings tickets → lower support cost / less rage-churn. Flag every assumed link (ticket volume → churn is an assumption unl