Verification Patterns
Skill Purpose: Verify sub-agent work against original requirements and standards
Core Skill Pattern
Objective: Systematically validate that sub-agent work products meet the original task requirements, quality standards, and integration criteria.
Universal Verification Process:
- •Requirement Validation: Verify work addresses original task completely
- •Quality Standards Check: Ensure work meets established quality gates
- •Integration Verification: Confirm work integrates with existing system
- •Documentation Review: Validate documentation is complete and accurate
- •Acceptance Decision: Approve, request revisions, or reject with specific feedback
Key Verification Dimensions:
- •Completeness: All requirements addressed
- •Correctness: Implementation matches specifications
- •Quality: Meets coding and documentation standards
- •Integration: Works with existing system components
- •Maintainability: Code is readable and maintainable
Project-Specific Verification Criteria
Customize per project:
- •Quality gate strictness levels
- •Documentation requirements
- •Integration testing depth
- •Performance benchmarks
- •Security validation requirements
Example Verification Workflow
Note: This is an example pattern for Architecture Department Head verification of sub-agent work.
Phase 1: Initial Requirements Check
Questions to Answer:
- •Does the work product address the original task completely?
- •Are all specified requirements implemented?
- •Are there any missing components or functionality?
Acceptance Criteria:
- • All original requirements addressed
- • No scope creep or missing features
- • Requirements traceability maintained
Phase 2: Quality Standards Validation
Check Areas:
- •Code follows established patterns and conventions
- •Documentation is complete and accurate
- •Testing coverage meets project standards
- •Performance requirements satisfied
Acceptance Criteria:
- • Code quality gates passed
- • Documentation complete
- • Tests pass and cover requirements
- • Performance benchmarks met
Phase 3: Integration Verification
Verification Steps:
- •Test integration with existing system
- •Verify no breaking changes
- •Confirm dependencies are properly managed
- •Validate deployment readiness
Acceptance Criteria:
- • Integration tests pass
- • No breaking changes introduced
- • Dependencies properly configured
- • Deployment ready
Phase 4: Documentation Review
Documentation Requirements:
- •Implementation details documented
- •Usage instructions provided
- •Maintenance guidelines included
- •Change requests updated
Acceptance Criteria:
- • Technical documentation complete
- • User guides provided
- • Maintenance procedures documented
- • Project artifacts updated
Verification Decision Matrix
| Outcome | Criteria | Next Action |
|---|---|---|
| Approve | All phases pass, no critical issues | Mark task complete, update project status |
| Request Revisions | Minor issues, specific fixes needed | Return to sub-agent with detailed feedback |
| Reject | Major issues, fundamental problems | Escalate to Company Head, reassign task |
Example Feedback Templates
Revision Request Template
code
REVISION REQUIRED - [Task Name] Issues Found: - [Specific issue 1 with location] - [Specific issue 2 with location] Expected Fixes: - [Specific fix 1] - [Specific fix 2] Return Deadline: [Date/Time] Verification Method: [How to verify fixes]
Rejection Template
code
TASK REJECTED - [Task Name] Reason for Rejection: - [Critical issue 1] - [Critical issue 2] Impact Assessment: - [How this affects project timeline] - [Resources needed to resolve] Recommendation: - [Escalate/reassign/restart]
Stop Conditions
STOP verification and escalate if:
- •Requirements are ambiguous or conflicting
- •Work product has fundamental architectural issues
- •Quality standards are not met significantly
- •Integration would break existing system
- •Sub-agent is unresponsive to feedback
PAUSE verification if:
- •External dependencies are blocking verification
- •Testing environment is unavailable
- •Documentation is incomplete for verification
Verification Tracking
Maintain verification log for each task:
- •Task ID and description
- •Sub-agent assigned
- •Verification phases completed
- •Issues found and resolutions
- •Final decision and timestamp
- •Lessons learned for future tasks
Integration with Project Management
Update project artifacts after verification:
- •Mark tasks as complete/in-progress/rejected
- •Update project timeline based on verification results
- •Document quality metrics and trends
- •Identify process improvements for verification workflow