business-analystlisted
Install: claude install-skill marcioaltoe/roundfix
# Business Analyst
Convert exploration into decisions. Three modes, picked by what the caller needs; `write-idea` uses the first two, executive deliverables use the third.
## Mode 1 — Feature scoring (for idea/PRD discovery)
Score a feature idea so its priority is an argument, not a feeling:
1. **Six-criteria assessment** — each scored `Must do / Strong / Maybe / Pass`, each score justified in one line citing research or codebase findings:
| Criteria | Question |
| ------------------- | --------------------------------------------------- |
| **Impact** | How much more valuable does this make the product? |
| **Reach** | What % of users would this affect? |
| **Frequency** | How often would users encounter this value? |
| **Differentiation** | Does this set us apart or just match competitors? |
| **Defensibility** | Is this easy to copy or does it compound over time? |
| **Feasibility** | Can we actually build this? |
2. **Leverage type** — Quick Win (small effort, disproportionate value), Strategic Bet (larger effort, potentially transformative), or Compounding (gets more valuable over time: data effects, habit formation, network effects).
3. **KPIs** — 3 to 6, each with a numeric target ("> 30%", "< 200ms", "-80%") and a concrete, implementable measurement method. A KPI nobody can measure is a wish.
4. **Viabil