assumption-bounty

Featured

Extract every hidden assumption from a plan or document and put a price on each one — what it costs if wrong, what it costs to test. Use before committing to anything whose author says 'obviously' or whose spreadsheet has hardcoded cells: the bounty hunt makes the invisible load-bearing beliefs explicit and tells you which three to test this week. Produces the assumption ledger (priced and ranked), the cheapest test for each dangerous one, and the document's honest confidence statement.

AI & Automation 1,231 stars 221 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Assumption Bounty Every plan is a stack of beliefs wearing a costume of facts. Most die from an assumption nobody wrote down — because unwritten assumptions can't be tested, assigned, or noticed when they quietly become false. The bounty hunt pays by the find: every hidden belief extracted, priced, and ranked by (cost if wrong) ÷ (cost to test). ## Required Inputs - **The document** — plan, model, PRD, forecast, strategy. Spreadsheet-backed documents: include the key hardcoded numbers; each one is an assumption in a trench coat. - Optional: which assumptions the team already knows about — the bounty only pays for *hidden* ones, and knowing the acknowledged list sharpens the hunt. ## Where Assumptions Hide - **In verbs**: "users will migrate" (will they?), "the team can absorb" (can it?) - **In adjectives**: "conservative estimate", "simple integration", "standard terms" - **In silence**: what the document never mentions — pricing pages that assume no competitor response, hiring plans that assume no attrition - **In hardcoded numbers**: every constant in the model (conversion 3%, CAC $400) is a belief with a confidence interval nobody stated - **In the past tense**: "as we saw in the pilot" — assuming the pilot generalises - **In org charts**: "marketing will drive awareness" assumes a team's priorities that were never negotiated ## Output Format 1. **The ledger** — table, ranked by danger score: assumption (quoted or reconstructed) | where it hides | cost if wrong (o...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
6 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

assumption-inventory

Surface and confirm the load-bearing assumptions behind a task before a long or expensive run — goal, root, what may be edited, what is off-limits, what done means, and open questions — separating what can be cited from what is being guessed, so bad direction is caught before time is burned. Also pressure-tests the plan's acceptance criteria, flagging any that are weak or built on unproven assumptions, and asks the blocking uncertainties (scope boundaries, interpretations, soft "done" bars) as structured questions. Use at the start of a multi-step or high-cost task, when resuming ambiguous or handed-off work, or whenever the target is not crisply stated and you are about to commit to a long run.

3 Updated today
adamlinscott
AI & Automation Listed

assumption-audit

Find and challenge hidden assumptions in a plan, prompt, bug report, design, or AI-generated answer. Use when claims are unverified, something is called obvious or safe, or a plan depends on external behavior. NOT for confirmed requirements or tiny mechanical edits.

0 Updated today
alinafe82
Testing & QA Listed

assumption-mapper

Discovery-stage skill: breaks a product idea into its load-bearing assumptions, ranked riskiest-first, each tagged testable/untestable with a proposed test. Use when the user pitches an idea and asks what it depends on — 'map the assumptions', 'what are we betting on', 'what could kill this', 'what needs to be true', 'riskiest assumption first' — or when /pm routes such a request here. Do NOT use to write the PRD or spec (Build stage), to size the market (opportunity-sizer's job), for knowledge questions about assumption-testing methods, or for analyzing non-product documents.

1 Updated 6 days ago
Abhillashjadhav