Comprehensive quality validation command that forces rigorous self-review before marking work complete. Ensures production-ready deliverables through multi-angle analysis, completeness verification, and quality gate enforcement.
/plugin marketplace add claudeforge/marketplace/plugin install quality-validator@claudeforge-marketplaceThe Quality Validator command provides a structured, comprehensive approach to verifying that work is truly complete and production-ready. It prevents premature completion claims by enforcing rigorous self-review across multiple dimensions, ensuring all deliverables meet professional standards before being marked as done.
In software development, declaring something "done" prematurely leads to:
This command combats these issues by enforcing a mandatory quality gate that validates completeness across multiple angles before allowing completion.
Before validating, clearly define what "complete" means for this specific task:
Questions to Answer:
Define Completeness:
Complete = All Requirements Met + Quality Standards Satisfied + No Known Issues + Documented + Tested
Document Interpretation:
Approach the validation from multiple perspectives to ensure comprehensive coverage:
Question: Does it do what it's supposed to do?
Validation checklist:
Question: Is it built well?
Validation checklist:
Question: Has it been properly tested?
Validation checklist:
Question: Can others understand and use it?
Validation checklist:
Question: Is it usable and intuitive?
Validation checklist:
Question: Can it be deployed, monitored, and maintained?
Validation checklist:
After multi-angle analysis, perform detailed review:
Code Review (if applicable):
Logic Review:
Integration Review:
Each quality gate must pass before proceeding:
Identify and assess risks before declaring complete:
Risk Categories:
Technical Risks
Business Risks
Operational Risks
Risk Matrix:
For each identified risk:
- Likelihood: Low / Medium / High
- Impact: Low / Medium / High
- Mitigation: Planned action or acceptance
- Owner: Who is responsible
Blocker Assessment:
Final checklist before declaring done:
Requirement Traceability:
Quality Standards:
Production Readiness:
Knowledge Transfer:
Rate each dimension on a scale of 1-10:
Functional Completeness: __/10
Technical Quality: __/10
Testing Coverage: __/10
Documentation: __/10
User Experience: __/10
Production Readiness: __/10
TOTAL: __/60
Scoring:
54-60: Excellent - Production ready
48-53: Good - Minor improvements recommended
42-47: Fair - Significant gaps, not ready
<42: Poor - Major work required
Minimum threshold: 48/60 required to declare complete
Problem: Untested in production-like environment Validation: Test in staging/pre-prod environment
Problem: Documentation never happens Validation: Documentation is required for completion
Problem: Edge cases cause production bugs Validation: All reasonable edge cases must be handled
Problem: Regressions and hidden bugs Validation: Testing is mandatory, not optional
Problem: Technical debt and quality degradation Validation: Must meet quality standards, not just "work"
When invoked with /double-check $ARGUMENTS:
Parse Context: Understand what work was done (from arguments or recent activity)
Define Complete: Explicitly state what "complete" means for this task
Multi-Angle Analysis: Evaluate from all 6 angles (functional, technical, testing, docs, UX, ops)
Quality Gates: Verify each gate passes
Risk Assessment: Identify and assess risks
Completeness Score: Calculate overall completeness rating
Gap Analysis: List what's missing or incomplete
Recommendations: Provide specific actions to reach true completion
Decision: Is it actually complete? Yes/No with justification
Typical Flow:
1. Implement feature/fix
2. Run local tests
3. Initial self-review
4. Run /double-check command
5. Address identified gaps
6. Run /double-check again
7. Create pull request
8. Request peer review
Quality Metrics:
Success Indicators:
Usage: /double-check [task-description] [--strict] [--quick]
Flags:
--strict: Apply higher standards (55/60 minimum score)--quick: Fast validation focusing on critical dimensions onlyExamples:
/double-check # Validate recent work
/double-check user authentication feature # Validate specific feature
/double-check --strict # Apply stricter criteria
/double-check --quick bug fix # Quick validation of bug fix
The Quality Validator command enforces a culture of excellence by making "done" mean truly done. It systematically validates completeness across functional, technical, testing, documentation, user experience, and operational dimensions. By preventing premature completion and catching issues early, it reduces technical debt, improves quality, and builds stakeholder trust.
Use this command liberally - it's better to discover gaps before committing than to discover them in production.
Remember: Professional work isn't just functional - it's complete, tested, documented, and production-ready. This command helps you get there every time.
$ARGUMENTS
/double-checkAn easy way to force agent to think again if it's statement that the "Job is done and production ready" is actually done - usually it's not. Thanks to this command you don't have to check after the agent if they did their job.
/double-checkAn easy way to force agent to think again if it's statement that the "Job is done and production ready" is actually done - usually it's not. Thanks to this command you don't have to check after the agent if they did their job.
/double-checkAn easy way to force agent to think again if it's statement that the "Job is done and production ready" is actually done - usually it's not. Thanks to this command you don't have to check after the agent if they did their job.