assumption-bounty
FeaturedExtract 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.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- mohitagw15856
- Repository
- mohitagw15856/pm-claude-skills
- Created
- 5 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
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.
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.
managing-assumption-debt
Use when collaborating with a human over many sessions and unstated assumptions could silently compound into expensive misunderstandings - when a rule or preference is stated in absolute terms (never/always/all/every), when about to deviate from a stated preference, when forming a belief about what the collaborator knows or has built, before producing anything irreversible or externally-facing (resumes, public sites, published repos, sends), or when checking whether you and they still agree on where the project actually stands.