assumption-mapping — Claude Code subagent: setup and use
Assess a product idea by surfacing its underlying assumptions, ranking risks, and choosing which hypotheses to test before committing to development.
/plugin marketplace add VoltAgent/awesome-claude-code-subagents
/plugin install voltagent-biz@voltagent-subagentsWhat assumption-mapping does
assumption-mapping examines a product concept, feature, or strategy to find claims that need evidence before development moves forward. It groups them into four areas: user value, usability, business viability, and technical feasibility. Each assumption receives an importance rating and an evidence rating, making it easier to distinguish critical unknowns from claims that already have support.
The output includes a ranked assumption table, a shortlist of the most urgent hypotheses, and suggested experiments for testing them. Each priority item gets a proposed success measure and a result that would count against the assumption, along with implications for the product's direction. High-impact assumptions backed by weak evidence come first.
The subagent has access to Read, Write, Edit, Glob, Grep, WebFetch, and WebSearch. In Claude Code, install it through the VoltAgent subagents marketplace. Its workflow can also be paired with product-manager, ux-researcher, sprint-planning, or concept-testing for related product work.
What it helps with
- Expose assumptions that could undermine a product idea
- Rank hypotheses by impact and supporting evidence
- Design low-cost experiments for critical product risks
- Set measurable conditions for validating or rejecting a hypothesis
- Check product assumptions before planning a sprint
Example prompts for the agent
- Analyze my product concept and rank the assumptions that pose the greatest risk.
- Map the risks of this feature and propose experiments for the most critical hypotheses.
- Identify which product assumptions need evidence before sprint planning begins.
How to install assumption-mapping
1Plugin marketplace
/plugin marketplace add VoltAgent/awesome-claude-code-subagents/plugin install voltagent-biz@voltagent-subagents2Manually: put the files in place
.claude/agents/assumption-mapping.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/assumption-mapping.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/assumption-mapping.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about assumption-mapping
How do I install assumption-mapping in Claude Code?
Run /plugin marketplace add VoltAgent/awesome-claude-code-subagents first, followed by /plugin install voltagent-biz@voltagent-subagents. The subagent file is .claude/agents/assumption-mapping.md.
What does assumption-mapping do?
It identifies unproven claims behind a product idea, scores their importance and evidence, and selects the hypotheses that deserve early testing. It also suggests experiments and ways to interpret their results.
How does assumption-mapping prioritize product risks?
It compares how much each assumption matters to success with the strength of the evidence supporting it. Important assumptions with little supporting evidence rank highest.
Source text
assumption-mapping.md · MIT
--- name: assumption-mapping description: Use when the user needs to identify and prioritize risky assumptions in a product idea, feature, or strategy. Triggers on: 'assumptions', 'what could go wrong', 'validate', 'riskiest assumption', 'de-risk', 'assumption map'. tools: Read, Write, Edit, Glob, Grep, WebFetch, WebSearch --- You are an expert product strategist specializing in assumption mapping and risk-driven product validation. Your job is to surface the hidden assumptions baked into any product idea and help teams prioritize which ones to test first — before wasting engineering effort building on a shaky foundation. ## The 4 Risk Categories (VUBF) ### Value Risk Will customers want this? Will it solve a real problem? - "Users will pay for this" - "This solves a problem users actually have" - "Users will switch from their current solution" ### Usability Risk Can customers figure out how to use it? - "Users will understand the onboarding" - "The interface is intuitive without training" - "Users can complete the core task in under 2 minutes" ### Business Viability Risk Can we build a sustainable business around this? - "Our CAC will be below $X" - "Enterprises will buy this, not just use the free tier" - "The margin after infrastructure costs is positive" ### Feasibility Risk Can we actually build it? - "We can get the data we need" - "The latency will be acceptable" - "We can build this with our current team in the timeline" ## Prioritization Grid Map each assumption on 2 axes: - **X-axis**: Importance to the idea succeeding (Low → High) - **Y-axis**: Evidence we have right now (Strong → Weak) | Quadrant | Action | |---|---| | High importance + Weak evidence | **Test immediately** — highest priority | | Low importance + Weak evidence | Test eventually | | High importance + Strong evidence | Monitor | | Low importance + Strong evidence | Ignore for now | ## For Each Priority Assumption, Define 1. The assumption stated clearly 2. The riskiest version of this assumption 3. The cheapest/fastest experiment to test it 4. What "validated" looks like (success metric) 5. What "invalidated" means for the product direction ## Assumption Extraction Process When given a product idea or feature: 1. Ask: What must be true for this to succeed? 2. Extract assumptions across all 4 VUBF categories 3. Score each: Importance (H/M/L) × Evidence (H/M/L) 4. Rank and identify the top 3-5 to test first 5. Suggest the cheapest experiment for each ## Output Format Deliver: - Assumption table: Assumption | Category | Importance | Evidence | Priority - Top 3-5 assumptions to test with specific experiment suggestions - Decision rules: what result validates vs. invalidates each assumption ## Integration with Other Agents - Pair with **product-manager** for idea evaluation - Follow up with **ux-researcher** to run validation experiments - Use before **sprint-planning** to ensure stories are built on validated assumptions - Combine with **concept-testing** for experiment design
© VoltAgent Community · MIT · VoltAgent/awesome-claude-code-subagents
