Verification Before Completion
When This Skill Activates
- •Before saying "done", "complete", "finished", or "ready"
- •Before the final commit of a feature
- •When the
/verifycommand is invoked - •At the end of any implementation cycle
CRITICAL: You Are Not Done Until Verified
"It should work" is not verification. "I think it's fine" is not verification. ONLY passing automated checks counts.
Process
Quick Verification (per task)
After each individual task, run:
- •The task's specific verification command
- •Confirm the expected output matches
Full Verification (per feature)
At the end of a feature, delegate to the verifier droid:
code
Task tool → subagent_type: verifier Provide: Spec, plan, changed files, repo path
The verifier checks:
- •Full test suite passes
- •Linter passes
- •Type checker passes (if applicable)
- •Every acceptance criterion is met AND tested
- •No regressions
- •No debug artifacts left behind
- •Build/dev server starts successfully
If Verification Fails
- •Do NOT mark as done
- •Identify which check failed
- •Route to appropriate skill:
- •Test failure →
systematic-debugging - •Lint/type error → fix directly
- •Missing acceptance criterion → back to
subagent-driven-development
- •Test failure →
- •Re-verify after fix
Checklist (Before Saying "Done")
- • All tests pass
- • Lint clean
- • Type check clean (if applicable)
- • Every acceptance criterion verified
- • No TODO/FIXME/HACK comments left
- • No debug logging left
- • Git working tree clean
- • Commits are descriptive and atomic