From product-skills
Evaluates product bets and shapes pitches using Shape Up appetite model and Bezos Type 1/Type 2 frameworks. For assessing initiative risks, resource allocation, and feature pitches.
npx claudepluginhub assimovt/productskills --plugin product-skillsThis skill uses the workspace's default tool permissions.
Size product bets by separating reversible from irreversible decisions and shaping work to fit an appetite. Most product bets are Type 2 decisions — reversible, low-cost to try, high-cost to deliberate. Move fast on those. Save deliberation for Type 1 decisions that are hard to undo.
Guides 4-step Shape Up process to shape work into pitches for betting. Supports established (fixed time, variable scope) and new product modes for cycle planning and PM coaching.
Prioritizes assumptions via Impact × Risk matrix, categorizes for action (test/implement/defer/reject), and suggests experiments with success metrics. For triaging or prioritization canvas.
Identifies, evaluates, and prioritizes design opportunities using impact-effort matrices, RICE scoring, Kano model, and value vs complexity frameworks. Outputs ranked roadmaps with rationale.
Share bugs, ideas, or general feedback.
Size product bets by separating reversible from irreversible decisions and shaping work to fit an appetite. Most product bets are Type 2 decisions — reversible, low-cost to try, high-cost to deliberate. Move fast on those. Save deliberation for Type 1 decisions that are hard to undo.
Type 1 (Irreversible): One-way doors. Hard to undo once committed.
Type 2 (Reversible): Two-way doors. Easy to undo or iterate.
Rule: Use lightweight process for Type 2. Use deliberate process for Type 1. Most product teams over-process Type 2 decisions and under-process Type 1 decisions.
When proposing a bet, structure it as a Shape Up pitch:
A specific story showing real pain. Not an abstract need — a concrete situation with a real user.
"When a PM finishes a customer interview, they spend 45 minutes transcribing notes into a PRD. By the time they're done, the emotional context is gone and the PRD reads like a requirements list."
How much time is this worth? Not how long it will take — how much you're willing to invest.
If you can't fit the solution in the appetite, reshape or kill it.
Breadboard-level, not pixel-perfect. Show the key interactions and flows without getting into visual design. Fat-marker sketches, flow diagrams, or written walkthroughs.
Known risks and unknowns that could blow up the timeline. For each: what's the risk and how will you mitigate it?
What's explicitly excluded. This is as important as what's included — it prevents scope creep during execution.
For larger bets, estimate expected value:
EV = (Upside x P(success)) - (Downside x P(failure)) + Learning Value
Built on Shape Up (Basecamp) and Jeff Bezos's Type 1/Type 2 decision framework. Skills from productskills.