epic-verifier

Use when all implementation tasks in an epic are closed, before calling finishing-a-development-branch

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "epic-verifier" with this command: npx skills add schlenks/superpowers-bd/schlenks-superpowers-bd-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

CheckQuestionEvidence Required
YAGNIBuilt only what requested?List code not in plan
DriftMatches spec?Deviations with file:line
Test CoveragePaths tested?Untested functions
RegressionsAll tests pass?Test suite output
DocumentationDocs updated?Outdated locations
SecurityNo vulnerabilities?Concerns or "none"
Rule-of-Five>50 line files reviewed?Per-file 5-pass results

Dispatch

Use template at ./verifier-prompt.md:

Task tool:
  subagent_type: "general-purpose"
  model: "sonnet"  # or "opus" for max-20x
  description: "Epic verification: {epic_id}"
  prompt: [use template]

Required context: {epic_id} (verifier self-reads from beads), base SHA, head SHA, test command.

Model Selection

TierModelRationale
max-20xopusCatches subtle issues
max-5xsonnetGood quality/cost balance
pro/apisonnetVerification quality matters

Integration

Mandatory gate: all impl tasks closed -> dispatch epic-verifier -> PASS -> finishing-a-development-branch / FAIL -> fix and re-verify.

Red Flags - Verification Theater

Claim Without EvidenceReject Because
"YAGNI passed"Must list what was compared
"Tests pass"Must show test output
"No security issues"Must list what was checked
"Rule-of-five done"Must show per-file findings

Evidence missing = reject verification.

Reference Files

  • references/edge-cases.md: Unusual epic shapes (no artifacts, no tests, review-only)
  • references/common-failures.md: Verification being skipped or rubber-stamped
  • references/example-output.md: Output format reference for verification report
  • references/why-separation-matters.md: Pushback on why dedicated verifier is needed
<!-- compressed: 2026-02-11, original: 519 words, compressed: 327 words -->

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

finishing-a-development-branch

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

rule-of-five-code

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

subagent-driven-development

No summary provided by upstream source.

Repository SourceNeeds Review