Index of every page on this site: llms.txt
All skills
deanpeters avatar

/assumption-mapping

@476ae12
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/assumption-mapping

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplessample-industrial.md

≈538 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Assumption Mapping Example: Industrial

Idea: a bracket kit that lets NFA-200 sites migrate to the NFA-500 in one shift. Decision: fund tooling for the bracket kit (long lead time, hard to reverse).

Why this example exists: in hardware the decision is hard to undo, so evidence weighs more, and the riskiest beliefs are about the plant floor and the channel, not the product.


## Assumptions
| # | Assumption | Type | Role | Imp. | Evidence | Strength |
|---|---|---|---|---|---|---|
| 1 | Plants can't give up a weekend of production | D | Plant manager | H | 6 of 9 interviews | Some-strong |
| 2 | The bracket kit makes the swap fit a single 8-hour shift | U | Technician | H | one pilot site | Weak |
| 3 | Existing programs import without rewriting | F | Engineer | H | test report T-114 (partial) | Some |
| 4 | Partners will stock the kit | V | Distributor | M | one partner said so | Weak |
| 5 | Plants will pay for the kit on top of the controller | V | Procurement | H | **none** | None |
| 6 | The kit keeps UL listing unchanged | V | Compliance | H | **not assessed** | None |
| 7 | Installers will follow the torque spec | U | Partner crew | M | observed twice | Weak |

## Map
**Test first:** 2, 5, 6
**Monitor:** 1, 3 (some evidence; check at pilot)
**Park:** 4, 7 (revisit after tooling decision)

## Top three
| # | Assumption | Kill condition | Test |
|---|---|---|---|
| 6 | Bracket kit keeps UL listing | Assessor says re-evaluation is required | Ask the assessment body before tooling |
| 5 | Plants pay for the kit | Fewer than 3 of 6 plants will quote it separately | Quote the kit to six plants (procurement included) |
| 2 | Swap fits 8 hours | Two of three pilot swaps exceed 8 hours | Three timed pilot swaps |

What to learn from this

  • The listing assumption (#6) could void the whole kit, and it had no evidence at all. It outranks every desirability question.
  • Evidence from one pilot is weak. One site is a story, not a sample.
  • Test order follows reversibility: the cheapest, most fatal question (the assessor) goes first, before tooling money is committed.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts7d3 checks · Risk SAFE
  • Gen Agent Trust Hub7d

    The assumption-mapping skill is a decision-support tool for identifying and ranking project risks. Analysis found no malicious patterns, unauthorized network activity, or hidden code. The skill operates entirely within the agent's safe execution environment.

  • Socket7d

    No alerts

  • Snyk7d

    Risk: LOW · No issues

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[the idea or plan, and the decision it supports]
type
component
theme
validation-experiments
Other metadata
intent
Surface the assumptions hiding inside an idea, a plan, or a business case, sort them into desirable, usable, viable, feasible, and ethical risk types, and place each on an importance by evidence map so the team tests the few that can sink the idea first. Output is a ranked list that feeds the de-risking skills.
best_for
[
  "Finding what an idea silently depends on before building or funding it",
  "Deciding which belief to test first when you cannot test everything",
  "Turning a confident plan into a short list of testable bets",
  "Giving a team a shared picture of what is known versus believed"
]
scenarios
[
  "We're about to commit a quarter to this feature. What are we assuming?",
  "Which of these 30 beliefs should we test first?",
  "The business case says 20% attach. What has to be true for that?",
  "Map the assumptions behind our retrofit migration plan"
]
estimated_time
30-60 min

README badge

README badge for deanpeters/product-manager-skills/assumption-mapping