epic-verifier
Epic Verifier
Dedicated verification agent for epic completion. Runs after all implementation tasks close, before finishing-a-development-branch. Builders build, verifiers verify -- separation prevents self-certification.
REQUIRED BACKGROUND: Read superpowers-bd:verification-before-completion, superpowers-bd:rule-of-five-code, and superpowers-bd:rule-of-five-tests SKILL.md files.
Trigger: All implementation tasks in epic show status: closed
Do NOT use: mid-epic (tasks still open), for single-task (use verification-before-completion), as substitute for per-task code review.
Quick Reference
| Check | Question | Evidence Required |
|---|---|---|
| YAGNI | Built only what requested? | List code not in plan |
| Drift | Matches spec? | Deviations with file:line |
| Test Coverage | Paths tested? | Untested functions |
| Regressions | All tests pass? | Test suite output |
| Documentation | Docs updated? | Outdated locations |
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.
8rule-of-five-tests
Use when writing 50+ lines of test code, adding test suites, or before claiming test work complete - apply 5 focused passes (Draft, Coverage, Independence, Speed, Maintainability) to catch issues single-shot generation misses
8systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
8