Skip to content

borghei/Claude-Skills / project-management/discovery/opportunity-solution-tree

opportunity-solution-tree

Verified

Maps one outcome to customer opportunities, 3+ solutions each and assumption tests, then audits the tree. Use when prioritizing discovery work, mapping solutions to a problem, or checking whether a roadmap moves outcomes.

assets/ost_template.md

View on GitHub
# Opportunity Solution Tree — Template

**Tree name:** [outcome + quarter; e.g., "Activation Q3"]
**Outcome owner:** [team / PM]
**As of:** [date]
**Last updated:** [date]
**Review cadence:** weekly (every [day])

---

## Outcome

> [Single sentence: behavioral or business metric, with baseline + target + timebox]

**Type:** behavioral / business
**Baseline:** [current value]
**Target:** [target value]
**Timebox:** [Q3 2026 / 6 months / etc.]
**Within team's influence:** yes / no (if no, decompose more)

---

## Opportunities

### O1 — [customer pain / need]
- **Evidence:** [interview-N, ticket-IDs, analytics link]
- **Size estimate:** [% of users affected, severity, frequency]
- **Prioritization:** high / medium / low

**Solutions:**

#### O1-S1 — [solution]
- **Cost / effort:** [S / M / L]
- **Risk:** [low / med / high]
- **Assumption tests:**
  - [Test name] — [type] — [success criterion] — [timebox] — [owner]
  - [Test 2]
- **Status:** brainstormed / testing / passed / killed / shipped

#### O1-S2 — [alternative solution]
[same structure]

#### O1-S3 — [alternative solution]
[same structure]

---

### O2 — [opportunity]
- **Evidence:**
- **Size estimate:**
- **Prioritization:**

**Solutions:**
#### O2-S1 — ...
#### O2-S2 — ...
#### O2-S3 — ...

---

### O3 — [opportunity]
[same structure]

---

## Assumption test backlog

| Test | Solution | Type | Success criterion | Timebox | Owner | Status |
|------|----------|------|-------------------|---------|-------|--------|
| | | interview / prototype / A/B / WoZ / smoke | | | | planned / running / done |

---

## Test results log

| Date | Test | Solution | Result | Decision |
|------|------|----------|--------|----------|
| | | | passed / mixed / failed | promote / iterate / kill |

---

## Solutions graveyard

| Solution | Why killed | Date |
|----------|------------|------|
| | | |

---

## Notes

- Weekly review: [day + time]
- Customer interview goal: [N per week]
- Outcome refresh: [next checkpoint date]
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall