using-superpowers
Using Superpowers (the 1% Rule dispatcher)
This is the keystone that makes the superpowers skill library actually fire. Without it, you tend to improvise — re-deriving methodology that the dedicated skills already encode. With it, the cost of trying the right skill is low and the cost of skipping it is high.
The 1% Rule
If there is even a 1% chance one of the user-invocable superpowers skills is the right tool for what the user just asked, invoke it explicitly via the Skill tool — don't improvise.
The cost of trying the right skill and finding it's a poor fit is one extra Skill invocation. The cost of improvising past the right skill is re-deriving structure the skill already encodes, missing the BDD discipline / per-batch evaluator / checklist evolution that the skill ships, and producing a worse outcome.
When in doubt, invoke. The ## CRITICAL: Bail-Out Check section in each skill (brainstorming, writing-plans, executing-plans, systematic-debugging) will exit cheaply if the work is genuinely trivial — you have not been over-invoking, you have been letting the skill self-select scope.