メニュー
Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.
Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.
Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.
Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.
Turn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.
Generate rigorous stakeholder challenge questions for proposal or meeting preparation.
Analyze competitors using Porter's four-component model - drivers, assumptions, strategy, capabilities.
| name | assumption-mapping |
| description | Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on. |
Generate and categorize assumptions underlying a product strategy.
Early in product development to surface and document what you're betting on.
Organize assumptions into four categories:
| Category | Focus | Example Questions |
|---|---|---|
| Desirability | Will users want this? | Problem severity, willingness to pay, switching triggers |
| Feasibility | Can we build it? | Technical risks, data needs, integrations, security |
| Viability | Will it make money? | Pricing, margins, retention, unit economics |
| Usability | Can users use it? | Task success, learnability, error tolerance |
Document:
For each category, create at least 5 assumptions:
Format:
Good example:
Each assumption should be:
Four lists of 5+ assumptions each:
Each with statement and impact if wrong.
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
