From majestic-company
Provides Markdown templates for assumption mapping, riskiest assumption tests (RAT), and product hypotheses to prioritize risks and plan validation experiments for product ideas.
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-companyThis skill uses the workspace's default tool permissions.
Frameworks for identifying, prioritizing, and testing product assumptions.
Use this skill when the user asks to "map assumptions", "identify assumptions", "what are we assuming", "assumption audit", "what could go wrong with this idea", "test our assumptions", "what do we need to validate", "identify our riskiest assumption", or when reviewing an idea or PRD and wants to surface hidden bets before building. Do NOT use this skill for general risk analysis — that is part of the pre-mortem skill.
Prioritizes assumptions via Impact × Risk matrix, categorizes for action (test/implement/defer/reject), and suggests experiments with success metrics. For triaging or prioritization canvas.
Activate for: assumption, hypothesis, assumption map, MVP, minimum viable product, lean startup, what assumptions am I making, test my idea, what could go wrong, assumption risk, validate assumption, kill my idea, stress test, what should I test first, MVP design, MVP scoping, what to build, minimum feature set, success criteria, failure criteria, pivot criteria, build plan, riskiest assumption, leap of faith assumption, critical assumption. NOT for: idea generation (use idea), customer discovery (use discovery), pilot results analysis (use validate).
Share bugs, ideas, or general feedback.
Frameworks for identifying, prioritizing, and testing product assumptions.
## Assumption Map
### Desirability (Will they want it?)
| Assumption | Evidence For | Evidence Against | Risk Level |
|------------|--------------|------------------|------------|
| [Users want X] | [data] | [data] | High/Med/Low |
### Viability (Will it work for the business?)
| Assumption | Evidence For | Evidence Against | Risk Level |
|------------|--------------|------------------|------------|
| [Users will pay $X] | [data] | [data] | High/Med/Low |
### Feasibility (Can we build it?)
| Assumption | Evidence For | Evidence Against | Risk Level |
|------------|--------------|------------------|------------|
| [We can integrate with X] | [data] | [data] | High/Med/Low |
### Riskiest Assumption to Test Next
**Assumption:** [The one with highest risk + least evidence]
**Test:** [Cheapest way to validate/invalidate]
**Success Criteria:** [Specific threshold]
**Timeline:** [Days/weeks]
## Hypothesis: [Short name]
**We believe that** [building this feature/making this change]
**For** [target user segment]
**Will result in** [expected outcome/behavior change]
**We will know we're right when** [measurable success criteria]
### Riskiest Assumption
[The assumption that if wrong, invalidates the hypothesis]
### Minimum Test
[Cheapest/fastest way to validate]
- Type: [Prototype/Fake door/Concierge/etc]
- Duration: [X days/weeks]
- Sample size: [N users]
### Decision Criteria
- **Ship if:** [specific threshold met]
- **Iterate if:** [mixed signals, specify]
- **Kill if:** [specific threshold not met]
| Assumption Type | Test Method | Timeline |
|---|---|---|
| Desirability | Fake door, landing page | Days |
| Usability | Prototype testing | Days |
| Value | Concierge MVP | Weeks |
| Feasibility | Technical spike | Days |
| Viability | Pre-sales, LOIs | Weeks |
Priority = Risk Level × Impact if Wrong × Cost to Test (inverse)
Test assumptions that are: