Assumption map
Skill eltntawy/idea-discovery-playbook/skills/assumption-map
16 agent skills to validate software ideas before you build — Mom Test interviews, JTBD, market research, pretotype tests, unit economics, and go/no-go scorecards. For Cursor, Claude Code & skills.sh.
npx -y skills add eltntawy/idea-discovery-playbook --skill assumption-mapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Maps riskiest assumptions on importance vs evidence, prioritizes falsification tests, and maintains an assumption ledger for software idea validation. Use when asking what to test first, assumption mapping, riskiest assumption, or pretotyping priorities.
SKILL.md
2.3 KB, as published. Nobody here has run it
Assumption Map
Surface what must be true for the idea to work. Link each assumption to one experiment in validation-experiments.
Workflow
- Brain-dump assumptions — problem exists, buyers pay, channel works, we can build, timing, regulation, etc.
- Score each on importance (1–5) and evidence (1–5, from
idea-scorecardhierarchy). - Plot mentally: prioritize high importance + low evidence.
- Pick top 3–5 to test this sprint.
- Assign cheapest falsifying test per row.
- Update ledger after each experiment.
2×2 guidance
| Low evidence | High evidence | |
|---|---|---|
| High importance | Test now | Monitor |
| Low importance | Defer | Ignore for now |
Assumption ledger
| ID | Assumption | Importance | Evidence tier | Test method | Success | Fail (kill) | Status |
|---|---|---|---|---|---|---|---|
| A1 | open |
Status: open | testing | validated | killed
Test method hints
| Assumption type | Often use |
|---|---|
| Problem exists | problem-discovery interviews |
| Willingness to pay | Priced fake door / pre-sale |
| Market size | market-sizing + desk research |
| Can reach buyer | Smoke test + paid traffic |
| Solution workflow | Concierge or Wizard of Oz |
| Founder can win | feasibility-gate |
Kill rule
If a high-importance assumption hits its fail threshold, stop or pivot — update idea-scorecard and discovery/INDEX.md decision.
Output
Save to discovery/<topic-slug>/research/YYYY-MM-DD-<topic-slug>-assumptions.md.
Copy open rows into idea-scorecard assumption ledger before scoring.