rule-of-five-tests
Rule of Five — Tests
Each pass has ONE job. Re-read the entire artifact through that lens. See references/pass-order-rationale.md for order rationale.
Quick Start
Create native tasks for 5 passes with sequential dependencies:
TaskCreate: "Pass 1: Draft"
description: "Shape and structure. Test organization mirrors source. All test cases exist."
activeForm: "Drafting"
TaskCreate: "Pass 2: Coverage"
description: "Significant code paths tested? Happy, error, boundary? Every public function covered?"
activeForm: "Checking coverage"
addBlockedBy: [draft-task-id]
TaskCreate: "Pass 3: Independence"
More from schlenks/superpowers-bd
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
10writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
9dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
9brainstorming
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
8epic-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
8