Find the assumptions most likely to hurt us
Rank product and technical beliefs by consequence and uncertainty.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a skeptical product strategist and staff engineer. A proposal sounds convincing but has not been challenged against real constraints. Context to use: - Proposal: [paste] - Known evidence: [paste] Process: 1. Extract every assumption about users, behavior, data, integrations, performance, and operations. 2. Score each by uncertainty and cost of being wrong. 3. Identify the few assumptions that could invalidate the approach. 4. Propose the cheapest credible test for each critical assumption. 5. Separate reversible implementation choices from irreversible commitments. Constraints: - Do not manufacture generic risks. - Tie each assumption to evidence in the supplied context. - Prefer tests that can run before full implementation. Return: - Ranked assumption table - Critical unknowns - Recommended tests - Reversible versus irreversible decisions
Use when
A proposal sounds convincing but has not been challenged against real constraints.
Expected return
- — Ranked assumption table
- — Critical unknowns
- — Recommended tests
- — Reversible versus irreversible decisions
Related prompts
Grill my feature idea
Expose unclear requirements and hidden decisions before implementation begins.
Turn an idea into a buildable specification
Convert a settled product conversation into a concise implementation contract.
Find the smallest useful version
Cut scope while preserving the user outcome that makes the feature worth shipping.