assumption-maplisted

# Assumption Map Surface hidden assumptions behind a plan, feature, or decision. Rank them by risk (probability × impact if wrong), then propose the cheapest experiment that would credibly validate each. ## Usage ``` /assumption-map "<feature or decision to analyze>" # map assumptions for a specific thing /assumption-map # map assumptions behind the current task context /assumption-map --technical # focus on technical/architecture assumptions only /assumption-map --product # focus on user/market/business assumptions only ``` ## Behavior ### Step 1 — Establish the subject If `$ARGUMENTS` is provided, use it as the subject. Otherwise, ask: > What are we mapping assumptions for? (feature, technical decision, architecture choice, or product bet) ### Step 2 — Extract assumptions by category Generate assumptions across these four layers, using the subject as context: **Desirability assumptions** (do users want this?) - Users have the problem we think they have - Users will change their current behavior to use this - The UX we plan is how users expect to solve it - The benefit is compelling enough to overcome switching cost **Feasibility assumptions** (can we build it?) - The technology stack can support this without major re-architecture - The performance characteristics will meet requirements at scale - The required third-party APIs / data sources are accessible and reliable -