IMPERATIVE: Systematic quality assessment and improvement through efficient protocols. Command-driven quality workflows, objective scoring, continuous improvement focus.
DIMENSION WEIGHT CRITERIA
Task Completion 25% Solves stated problem completely
Code Quality 25% Maintainable, follows conventions
Professional Discipline 25% Proper tool usage, protocol adherence
Information Entropy 25% Valuable insights discovered/documented
TARGET SCORE: ≥7.5 overall | EXCELLENCE: ≥9.0 | MINIMUM: ≥6.0
assess quality [component]
EXECUTE Assessment:
1. Task Completion Score (1-10):
- Requirements fully met?
- Edge cases handled?
- User satisfaction achieved?
2. Code Quality Score (1-10):
- Follows Claude_Nexus conventions (KISS/YAGNI/DRY)?
- Maintainable by future developers?
- Appropriate error handling?
3. Professional Discipline Score (1-10):
- MCP tool hierarchy followed?
- Proper workflow protocols applied?
- Git Commitment Protocol executed?
4. Information Entropy Score (1-10):
- Surprising insights discovered?
- Valuable patterns documented?
- Knowledge applicable beyond current task?
CALCULATE: Weighted Average = (Sum of weighted scores) / 4
RESULT: Overall Score [X.X] / 10
EXECUTE Self-Critique Cycle:
PHASE 1 - CREATOR:
- Generate comprehensive initial solution
- Focus on functionality and requirements
- Document implementation decisions
- Optimize for user value delivery
PHASE 2 - CRITIC:
- Challenge all assumptions systematically
- Identify edge cases and failure modes
- Assess security, performance, integration risks
- Question design choices and alternatives
PHASE 3 - DEFENDER:
- Address each criticism systematically
- Implement improvements and fixes
- Validate solutions don't introduce regressions
- Document responses to criticisms
PHASE 4 - JUDGE:
- Compare original vs improved solution
- Apply 4-dimension quality assessment
- Determine if quality meets standards (≥7.5)
- Approve for completion or require iteration
Task Complexity Assessment:
HIGH-IMPACT (Full 4-Phase Cycle):
- New feature implementations
- Architectural decisions
- Security-sensitive changes
- Performance-critical code
MEDIUM-IMPACT (Critic + Defender minimum):
- Code refactoring
- Bug fixes affecting multiple components
- Integration implementations
LOW-IMPACT (Quick Self-Review):
- Simple bug fixes
- Documentation updates
- Minor configuration changes
validate readiness [task]
EXECUTE Readiness Check:
1. Requirements clearly understood?
2. Implementation approach planned?
3. Quality criteria defined?
4. Success criteria measurable?
5. Tools and dependencies available?
GATE: Cannot proceed until all criteria met
check progress [milestone]
EXECUTE Progress Validation:
1. mcp__serena__think_about_task_adherence
2. Current implementation quality assessment
3. Remaining work scope verification
4. Risk assessment and mitigation planning
5. Resource allocation adjustment if needed
GATE: Address deviations before continuing
validate completion [deliverable]
EXECUTE Completion Validation:
1. mcp__serena__think_about_whether_you_are_done
2. Full 4-dimension quality assessment
3. User acceptance criteria verification
4. Integration testing completion
5. Documentation and knowledge capture
GATE: Score ≥7.5 required for approval
EXECUTE Quality Improvement:
1. Identify specific quality dimension needing improvement
2. Apply targeted improvement strategy:
Task Completion Issues:
- Revisit requirements and acceptance criteria
- Implement missing functionality
- Address edge cases and error conditions
Code Quality Issues:
- Apply Claude_Nexus conventions (KISS/YAGNI/DRY)
- Improve maintainability and readability
- Enhance error handling and logging
Professional Discipline Issues:
- Follow MCP tool hierarchy properly
- Apply workflow protocols systematically
- Complete documentation requirements
Information Entropy Issues:
- Extract and document valuable insights
- Identify reusable patterns
- Capture learning for future reference
3. Re-assess quality after improvements
4. Iterate until target score achieved
EXECUTE Workflow Optimization:
1. Identify workflow bottlenecks or inefficiencies
2. Analyze root causes of quality issues
3. Design improved process incorporating lessons learned
4. Test improved workflow on representative tasks
5. Document optimized workflow patterns
6. Update quality protocols based on insights
Code Quality Patterns:
- Symbol-based editing over file-level changes
- Incremental implementation with testing
- Error handling at appropriate abstraction levels
- Clear separation of concerns
- Documentation of non-obvious decisions
Process Quality Patterns:
- MCP tool hierarchy strict adherence
- Systematic workflow protocol application
- Regular consciousness synchronization
- Information entropy focus in documentation
- Proactive quality assessment integration
Quality Anti-Patterns:
- Skipping tool hierarchy for convenience
- Implementing without clear requirements
- Ignoring edge cases and error conditions
- Verbose documentation of routine activities
- Quality assessment as afterthought
- Committing without proper review cycle
Quality Score History:
- Track scores across different task types
- Identify improvement trends over time
- Recognize quality pattern correlations
- Monitor consistency in quality achievement
Pattern Analysis:
- Which workflows consistently achieve high quality?
- What factors correlate with quality scores?
- Which improvement strategies are most effective?
- How does tool usage affect quality outcomes?
Improvement Indicators:
- Increasing average quality scores
- Reduced quality issue recurrence
- Faster quality assessment execution
- Better quality prediction accuracy
- Improved workflow efficiency
handle quality crisis [issue]
EXECUTE Crisis Management:
1. Immediate damage assessment and containment
2. Root cause analysis of quality failure
3. Systematic fix implementation with validation
4. Quality protocol review and improvement
5. Prevention strategy implementation
6. Team communication and learning capture
manage quality debt [area]
EXECUTE Debt Reduction:
1. Quality debt inventory and prioritization
2. Systematic debt reduction planning
3. Resource allocation for quality improvement
4. Progress tracking and milestone validation
5. Quality standard elevation and maintenance
Quality-Aware Tool Usage:
- Apply quality criteria in tool selection
- Use quality metrics to guide tool optimization
- Integrate quality assessment in tool workflows
- Document tool impact on quality outcomes
Quality Knowledge Management:
- Capture quality insights in memory system
- Use past quality patterns for current assessment
- Build quality pattern libraries from experience
- Track quality improvement over time
Quality-Enhanced Workflows:
- Embed quality gates in all major workflows
- Use quality metrics to optimize workflow design
- Apply quality patterns proactively in execution
- Continuous workflow improvement based on quality outcomes
QUICK QUALITY CHECKLIST:
□ Solves original problem completely
□ Handles obvious edge cases appropriately
□ Follows Claude_Nexus conventions and standards
□ Uses proper MCP tool hierarchy
□ Documents valuable insights discovered
□ Ready for review/deployment
SCORE: [Count checked items] / 6 * 10 = Quick Quality Score
COMPREHENSIVE QUALITY EVALUATION:
Task Completion Assessment:
□ All acceptance criteria met
□ Edge cases identified and handled
□ User workflow validated end-to-end
□ Integration points tested
□ Performance acceptable
SCORE: [X] / 10
Code Quality Assessment:
□ Follows KISS principle (appropriate simplicity)
□ Applies YAGNI (no unnecessary features)
□ Uses DRY appropriately (balanced abstraction)
□ Maintainable by future developers
□ Comprehensive error handling
SCORE: [X] / 10
Professional Discipline Assessment:
□ MCP tool hierarchy followed strictly
□ Workflow protocols applied systematically
□ Documentation updated appropriately
□ Git Commitment Protocol executed
□ Quality gates respected throughout
SCORE: [X] / 10
Information Entropy Assessment:
□ Surprising insights discovered and documented
□ Patterns applicable beyond current task
□ Anti-patterns identified and avoided
□ Knowledge captured for future reference
□ Learning contributes to skill development
SCORE: [X] / 10
OVERALL SCORE: (Sum of weighted scores) / 4 = [X.X] / 10
Quality Philosophy: Systematic assessment, continuous improvement, pattern recognition, excellence pursuit Quality Command: Assess → Improve → Validate → Document → Optimize Quality Integration: Embedded in workflows, enhanced by tools, preserved in memory