identify-business-problems

Ranks competing business problems and selects one to pursue using bottom-up sizing and risk-reward quadrants.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill identify-business-problems-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: identify-business-problems
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/identify-business-problems
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill identify-business-problems-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams facing multiple competing problems, stakeholder asks, or project ideas often pick the loudest voice or the most interesting build instead of the highest-value problem. This Skill forces an honest, evidence-based ranking so exactly one problem earns protected time before anything enters a roadmap. ## Core Features & Use Cases - Bottom-up opportunity sizing: Sizes every candidate from defensible counts (people affected × share hit × value lost), expressed as ranges with S/M/L classes — top-down TAM math is banned. - Risk-reward quadrant placement: Every candidate lands in a named quadrant cell with specifically named risks (time burn, wrong-problem risk, compounding loss) in both acting and not-acting directions. - Milestone anchoring and feasibility check: Nothing floats without a named outcome + number + date, and a capacity check (estimate ≤ available hours × 0.8) runs before any recommendation. - Use Case: A studio owner with 5 hours per week must choose between a website redesign, early-member churn, and unused class spots. The Skill sizes churn at $2.5k–4.5k/month, anchors it to the break-even milestone, verifies it fits capacity, and recommends it while deferring the redesign. ## Quick Start Ask the AI to identify and rank which business problem to solve first from your list of competing problems, stakeholder asks, or project ideas.

Frequently Asked Questions about identify-business-problems

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize which business problem to solve first?

Build one problem card per candidate, audit the evidence behind each, size each opportunity bottom-up as a range, place every card on a risk-reward quadrant, anchor survivors to a named milestone, then run a feasibility check against real capacity. Recommend exactly one problem and schedule, defer, or cut the rest.

What is bottom-up opportunity sizing?

Bottom-up sizing multiplies people or events affected per period by the share that actually hits the problem by the value lost per hit, using counts you can source. Top-down market-share math like "1% of a $10B market" is banned because it proves nothing about your specific business.

When should I not use a problem prioritization framework?

Skip it when the problem is already chosen and needs solution-free framing, when you are choosing among solution concepts for the same problem, or when it is pure calendar triage with no business problem behind it. This skill picks the problem; framing it is a separate step.

How do I check if a project fits team capacity before committing?

Estimate realistically using past actuals, multiplying first-of-kind gut estimates by 1.5. Count real available hours after standing commitments, plan to at most 80% of capacity, and verify the estimate fits the runway. If it fails, shrink scope, defer, or name what it displaces.

Why should every initiative anchor to a milestone?

A milestone is a named outcome plus a number plus a date, such as "140 members before the December lease decision." Work without a milestone floats and crowds out anchored work, so floaters must carry an explicit written reason or be cut.