Guides developer verification before handoff. Use when completing implementation, preparing for acceptance testing, or self-reviewing work before commit or PR.
This skill inherits all available tools. When active, it can use any tool Claude has access to.
Developer verification ensures the implementation is ready for acceptance testing.
Copy and track progress:
Developer Verification:
- [ ] All acceptance criteria manually tested
- [ ] Error cases verified
- [ ] Existing functionality not broken
- [ ] All automated tests pass
- [ ] Linting passes
- [ ] No debug prints left behind
- [ ] No TODO without context
- [ ] Story log updated
For each acceptance criterion:
Run the project's test suite:
# Example commands (adapt to your project)
npm test
deno task test
pytest
# Linting (adapt to your project)
npm run lint
deno lint
ruff check .
Check for:
console.log, print(), or debug statementsTODO commentsFill in "Acceptance Checks" section:
### Acceptance Checks
**Status: Pending Product Owner Review**
Developer verification completed:
- Tested all 5 acceptance criteria manually
- Verified error messages display correctly
- Confirmed existing features still work
- All 23 tests pass