Performs rigorous validation before marking a task complete. Use after execution - runs full test suite, validates against requirements.md and plan.md, delegates to verifier agent for peer review. Not done until tests pass AND user is satisfied.
/plugin marketplace add astrosteveo/claude-code-plugins/plugin install harness@astrosteveo-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Rigorous validation before completion. This is the peer review gate.
Not just new tests - the entire suite:
# Run all tests, not just changed ones
npm test # or pytest, go test, etc.
Check for:
Read requirements.md and check each success criterion:
## Requirements Validation
| Criterion | Status | Evidence |
|-----------|--------|----------|
| {criterion 1} | ✅/❌ | {how verified} |
| {criterion 2} | ✅/❌ | {how verified} |
Read plan.md and verify all steps completed:
## Plan Validation
| Step | Status | Commit |
|------|--------|--------|
| {nnn}-1 | ✅/❌ | {hash} |
| {nnn}-2 | ✅/❌ | {hash} |
Ensure tests are meaningful:
Real Harnesses
Coverage
Use the verifier agent for peer review simulation:
@verifier Review the changes for this task. Check:
- Code quality and patterns
- Test coverage and quality
- Security considerations
- Documentation accuracy
Incorporate feedback from the verifier.
Not complete until BOTH conditions are met:
Ask the user:
"Tests are passing. Does the implementation meet your expectations? Anything you'd like adjusted?"
Tests pass but user spots issues:
Tests fail:
Verifier finds issues:
When both conditions are met:
"All validations pass and you're satisfied with the implementation. This task is complete!
Summary:
- {X} tests passing
- All {N} requirements met
- All {M} plan steps complete
Ready to commit and wrap up?"
## Final Verification
### Tests
- [ ] Full test suite passes
- [ ] No new warnings
- [ ] Tests are meaningful (not superficial)
### Requirements
- [ ] All success criteria met
- [ ] Constraints respected
- [ ] Scope maintained
### Plan
- [ ] All steps completed
- [ ] Commits are atomic and logical
- [ ] No steps skipped
### Quality
- [ ] Code follows project patterns
- [ ] No security issues
- [ ] No performance regressions
### User
- [ ] User reviewed implementation
- [ ] User is satisfied
You may return to this phase when:
Re-run the full verification process.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.