verification-checklist
Use before marking any task complete to ensure all requirements are met
When & Why to Use This Skill
The Verification Checklist skill provides a rigorous, systematic framework for AI agents to validate their work before final delivery. It ensures high-quality output by mandating a 'Definition of Done' that includes clean diagnostics, successful builds, passing tests, and strict adherence to the user's original requirements, effectively preventing incomplete or broken task submissions.
Use Cases
- Software Development: Automating the final quality check for code changes by requiring clean LSP diagnostics and successful build/test cycles before task completion.
- Code Refactoring: Ensuring that structural changes do not introduce new linting errors or regressions by following a standardized evidence-based verification protocol.
- Requirement Validation: Cross-referencing the final implementation against the user's initial prompt to guarantee that all specific constraints and edge cases have been addressed.
- Quality Assurance: Standardizing the evidence required (such as exit codes and test logs) to provide a transparent and verifiable audit trail of task success.
| name | verification-checklist |
|---|---|
| description | Use before marking any task complete to ensure all requirements are met |
Verification Checklist
A task is NOT complete until all verification passes. No exceptions.
Completion Criteria
- All planned todo items marked done
- Diagnostics clean on changed files
- Build passes (if applicable)
- Tests pass (if applicable)
- User's original request fully addressed
Evidence Requirements
| Action | Required Evidence |
|---|---|
| File edit | lsp_diagnostics clean on changed files |
| Build command | Exit code 0 |
| Test run | Pass (or explicit note of pre-existing failures) |
| Delegation | Agent result received and verified |
NO EVIDENCE = NOT COMPLETE.
Verification Steps
1. Run Diagnostics
lsp_diagnostics on each changed file
2. Run Build (if project has build)
npm run build / cargo build / etc.
3. Run Tests (if project has tests)
npm test / cargo test / etc.
4. Check Against Original Request
Re-read the user's original request. Does your implementation:
- Address ALL requirements mentioned?
- Handle edge cases discussed?
- Follow any constraints specified?
If Verification Fails
- Fix issues caused by YOUR changes
- Do NOT fix pre-existing issues unless asked
- Report: "Done. Note: found N pre-existing lint errors unrelated to my changes."
Pre-existing Failures
If tests/build/lint were failing BEFORE your changes:
- Document the pre-existing failures
- Ensure you didn't make them worse
- Report them separately from your work
Before Final Delivery
- Cancel ALL running background tasks:
background_cancel(all=true) - Summarize what was done
- Note any caveats or follow-up items