pareto

What problem does it solve? Large tasks often hide a small set of causes that generate most of the outcome. This Skill applies the Pareto Principle to a request: it ranks the causes behind the work, spends roughly a fifth of the full effort on the interventions that address the top causes, and reports what that effort bought, so you can decide whether to fund the rest. ## Core Features & Use Cases - Cause ranking: Ranks causes by effect size using visible signals like error rates, coverage gaps, or file churn, and flags flat distributions where no vital few exist. - Budgeted execution: Spends about 20% of the full job's effort on the highest outcome-per-effort interventions, keeping the work coherent and the build unbroken. - Cut reporting: Reports the vital few causes, what the budget bought, and what remains, separating minor leftovers from unaffordable root causes. - Use Case: Ask for an 80/20 pass over a module with scattered bug reports; the Skill identifies the one confused component behind most failures, fixes what fits the budget, and prices the proper fix it could not afford. ## Quick Start Invoke /pareto with a request such as asking for an 80/20 pass over the test coverage gaps in the billing module.