opportunity-triage

Files (1)

• SKILL.md

SKILL.md (first lines)

# Opportunity Triage Skill

Use this skill when evaluating an idea before implementation.

Input idea:

```text
$ARGUMENTS
```

## Mission

Do not encourage the idea by default. Decide whether it deserves scarce build time.

## Required output

Write a structured triage memo with:

1. **Idea restatement** — one sentence.
2. **Buyer hypothesis** — who has the pain and who controls budget.
3. **Pain hypothesis** — urgent, expensive, frequent, or status-sensitive pain.
4. **Existing workaround** — spreadsheet, VA, agency, internal analyst, Zapier, dashboard, manual process, competitor tool.
5. **Existing spend** — what buyers already pay in money, hours, risk, churn, missed revenue, or compliance exposure.
6. **Distribution path** — the first reachable buyer channel.
7. **Fastest validation test** — one test executable in 24-72 hours.
8. **Scorecard** — score 1-10:
   - buyer pain
   - willingness to pay
   - urgency
   - buyer reachability
   - time to demo
   - technical feasibility
   - verification ease
   - distribution advantage
   - reusable asset value
9. **Verdict** — `BUILD`, `RESHAPE`, or `KILL`.
10. **Next action** — 3 concrete actions for the chosen verdict.

## Scoring discipline

- `BUILD` requires concrete buyer, urgent pain, reachable channel, fast validation, and credible verification.
- `RESHAPE` means the domain is promising but the current formulation is too vague, too horizontal, too hard to sell, or too slow to prove.
- `KILL` means the idea is mostly intellectual entertainment, commodity automation, low urgency, or distribution-poor.

## Durable output

If working in a repo, create or update:

```text
docs/profit/current-opportunity.md
docs/profit/decision-log.md
```

Append the verdict and date to the decision log.

From az9713/idea-to-capital, MIT.

More from az9713/idea-to-capital