rule-of-five-tests
No SKILL.md available for this skill.
View on GitHubMore from schlenks/superpowers-bd
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
9epic-verifier
Use when all implementation tasks in an epic are closed, before calling finishing-a-development-branch
8systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
8multi-review-aggregation
Use when dispatching code reviews for tiers with N greater than 1 (max-20x, max-5x) in subagent-driven development, or manually for critical changes over 200 lines or security-sensitive code
8finishing-a-development-branch
Use when ALL tasks in an epic or branch are closed and you are ready to integrate the entire body of work - never after individual task completions, never mid-epic
8rule-of-five-plans
Use when writing 50+ lines of plans, design docs, skill documents, or process documentation - apply 5 focused passes (Draft, Feasibility, Completeness, Risk, Optimality) to catch issues single-shot generation misses
7