Skip to content

deanpeters/Product-Manager-Skills / plugins/pm-discover/skills/assumption-mapping

assumption-mapping

Verified

List the assumptions behind an idea and rank them by importance and evidence. Use when a plan feels solid and you need to find the beliefs it rests on before you commit.

FileKindSize
SKILL.mdskill md12.6 KB
examples/sample-industrial.mdmarkdown2.1 KB
examples/sample.mdmarkdown2.3 KB
template.mdmarkdown1.4 KB

template.md

View on GitHub
# Assumption Mapping Template

Write each as a testable claim. Evidence you cannot name is "none". Quality checks at the bottom.

---

## 1. Frame
**Idea:** · **For whom:** · **Decision it supports:** · **Who must believe it:**

## 2. Assumptions

| # | Assumption (testable claim) | Risk type (D / U / V / F / E) | Role it matters to | Importance (H / M / L) | Evidence held (named) | Evidence strength | Tag |
|---|---|---|---|---|---|---|---|

Risk types: **D**esirable · **U**sable · **V**iable · **F**easible · **E**thical.
Evidence strength: strong (observed or paid) · some (stated intent) · weak (opinion) · none.

## 3. Map

| | Strong evidence | Weak evidence |
|---|---|---|
| **High importance** | Monitor: # | **Test first:** # |
| **Low importance** | Ignore: # | Park: # |

## 4. The top three

| # | Assumption | Why it ranks | Kill condition (result that changes or stops the idea) | Test (skill) |
|---|---|---|---|---|
| 1 | | | | |
| 2 | | | | |
| 3 | | | | |

## 5. Next
[Test this week / gather evidence / workshop / stop]

---

## Quality checks
- [ ] Every item is a testable claim, not a worry
- [ ] All five risk types are represented, including the boring ones
- [ ] Evidence is named behavior or data, never conviction
- [ ] The top three are high importance and weak evidence
- [ ] Each top assumption has a kill condition
- [ ] Each top assumption points to a test
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall