borghei/Claude-Skills / project-management/discovery/identify-assumptions
identify-assumptions
VerifiedSurfaces the assumptions behind a product bet, scores impact against confidence and picks the few to test first. Use when an idea feels right but is unproven, the team disagrees on risk, or before designing experiments.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.9 KB |
| assets/assumption_map_template.md | markdown | 3.8 KB |
| assets/sample_assumptions.json | config | 1.4 KB |
| assets/sample_assumptions_overloaded.json | config | 1.4 KB |
| examples/shared-dashboards-assumption-mapping.md | markdown | 14.3 KB |
| references/assumption-mapping-guide.md | markdown | 8.8 KB |
| references/methodology-and-tools.md | markdown | 10.1 KB |
| references/red-flags.md | markdown | 13.1 KB |
| scripts/assumption_tracker.py | script | 12.3 KB |
assets/assumption_map_template.md
View on GitHub# Assumption Map Template
## Context
| Field | Value |
|-------|-------|
| **Product / Feature** | |
| **Date** | YYYY-MM-DD |
| **Facilitator** | |
| **Participants** | PM: / Designer: / Engineer: |
| **Product Type** | New Product / Existing Product |
| **Categories Used** | 4 (existing) / 8 (new product) |
---
## Assumption Registry
| # | Assumption | Category | Confidence | Impact (1-10) | Risk Score | Quadrant |
|---|-----------|----------|-----------|:---:|:---:|----------|
| 1 | | Value | Low / Med / High | | | |
| 2 | | Usability | Low / Med / High | | | |
| 3 | | Viability | Low / Med / High | | | |
| 4 | | Feasibility | Low / Med / High | | | |
| 5 | | Ethics | Low / Med / High | | | |
| 6 | | Go-to-Market | Low / Med / High | | | |
| 7 | | Strategy | Low / Med / High | | | |
| 8 | | Team | Low / Med / High | | | |
**Risk Score Formula:** Impact x (1 - Confidence), where High=0.8, Medium=0.5, Low=0.2
**Quadrant Assignment:**
- **Test Now:** Impact >= 7 AND Confidence = Low or Medium
- **Proceed:** Impact >= 7 AND Confidence = High
- **Investigate:** Impact < 7 AND Confidence = Low
- **Defer:** Impact < 7 AND Confidence = Medium or High
---
## Risk Category Quick Reference
### Core 4 (All Products)
| Category | Key Question | Devil's Advocate Prompt |
|----------|-------------|------------------------|
| **Value** | Will customers want this? | "What if nobody actually has this problem?" |
| **Usability** | Can they figure it out? | "What if users cannot complete the task without help?" |
| **Viability** | Does the business case work? | "What if this costs more to maintain than it generates?" |
| **Feasibility** | Can we build it? | "What if the technical complexity is 3x our estimate?" |
### Extended 4 (New Products Only)
| Category | Key Question | Devil's Advocate Prompt |
|----------|-------------|------------------------|
| **Ethics** | Should we build this? | "What if this harms users we did not consider?" |
| **Go-to-Market** | Can we reach customers? | "What if our target segment is unreachable at viable CAC?" |
| **Strategy** | Does this align with our direction? | "What if leadership changes priorities next quarter?" |
| **Team** | Do we have the right people? | "What if the key skill gap takes 6 months to fill?" |
---
## Prioritization Matrix (Impact vs. Risk)
```
10 ┌─────────────────┬─────────────────┐
│ │ │
│ PROCEED │ TEST NOW │
I │ (move forward │ (experiment │
M │ with tripwire)│ immediately) │
P 7 ├─────────────────┼─────────────────┤
A │ │ │
C │ DEFER │ INVESTIGATE │
T │ (accept risk) │ (gather data) │
│ │ │
1 └─────────────────┴─────────────────┘
HIGH confidence LOW confidence
(low risk) (high risk)
```
Place each assumption's number on the matrix above.
---
## Action Plan: Test Now Assumptions
| # | Assumption | Why High Risk | Validation Method | Owner | Timeline | Status |
|---|-----------|--------------|-------------------|-------|----------|--------|
| | | | | | | Not Started |
| | | | | | | Not Started |
| | | | | | | Not Started |
---
## Tripwires: Proceed Assumptions
| # | Assumption | Monitoring Metric | Tripwire Threshold | Review Date |
|---|-----------|-------------------|-------------------|-------------|
| | | | | |
| | | | | |
---
## Notes
*Capture reasoning, debates, and additional context from the mapping session.*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |