Files
Claude-Code-Workflow/.claude/workflows/cli-templates/prompts/verification/cross-validation.txt
catlog22 0afbeac710 feat: Add workflow verification system with dual analysis
- Create /workflow:verify command for plan validation before execution
- Implement gemini strategic analysis and codex technical analysis
- Add cross-validation framework with user approval workflow
- Enhance brainstorm auto.md with comprehensive pre_analysis configuration
- Include specialized verification prompt templates for structured analysis

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-24 10:01:20 +08:00

65 lines
3.3 KiB
Plaintext

Cross-validation analysis of gemini strategic and codex technical assessments for workflow implementation plan:
## Required Cross-Validation Analysis:
1. **Consensus Identification**
- Identify areas where both analyses agree on issues or strengths
- Document shared concerns and aligned recommendations
- Highlight consistent risk assessments and mitigation strategies
- Establish priority consensus for implementation focus
2. **Conflict Resolution Analysis**
- Identify discrepancies between strategic and technical perspectives
- Analyze root causes of conflicting assessments
- Evaluate trade-offs between strategic goals and technical constraints
- Provide balanced recommendations for resolution
3. **Risk Level Synthesis**
- Combine strategic and technical risk assessments
- Establish overall implementation risk profile
- Prioritize risks by impact and probability
- Recommend risk mitigation strategies
4. **Recommendation Integration**
- Synthesize strategic and technical recommendations
- Resolve conflicting suggestions with balanced approach
- Prioritize recommendations by impact and effort
- Establish implementation sequence and dependencies
5. **Quality Assurance Framework**
- Establish combined quality metrics and success criteria
- Define validation checkpoints and review gates
- Recommend monitoring and feedback mechanisms
- Ensure both strategic and technical quality standards
## Input Analysis Sources:
- **Gemini Strategic Analysis**: Architecture, business alignment, strategic risks
- **Codex Technical Analysis**: Implementation feasibility, code quality, technical risks
- **Original Implementation Plan**: IMPL_PLAN.md, task definitions, context
## Output Requirements:
### Cross-Validation Summary:
- **Overall Assessment Grade** (A-F): Combined strategic and technical evaluation
- **Implementation Confidence** (1-10): Combined feasibility assessment
- **Risk Profile**: High/Medium/Low with specific risk categories
- **Recommendation Priority Matrix**: Urgent/Important classification
### Synthesis Report:
- **Consensus Areas**: Shared findings and aligned recommendations
- **Conflict Areas**: Divergent perspectives requiring resolution
- **Integrated Recommendations**: Balanced strategic and technical guidance
- **Implementation Roadmap**: Phased approach balancing strategic and technical needs
### User Approval Framework:
- **Critical Changes**: Must-implement modifications (blocking issues)
- **Important Improvements**: High-value enhancements (quality/efficiency)
- **Optional Enhancements**: Nice-to-have improvements (future consideration)
- **Trade-off Decisions**: User choice between competing approaches
### Modification Categories:
- **Task Structure**: Task merging, splitting, or reordering
- **Dependencies**: Dependency additions, removals, or modifications
- **Context Enhancement**: Requirements, acceptance criteria, or documentation
- **Technical Adjustments**: Implementation approach or tool changes
- **Strategic Alignment**: Business objective or success criteria refinement
Focus on balanced integration of strategic and technical perspectives. Provide clear user decision points with impact analysis and implementation guidance. Prioritize recommendations by combined strategic and technical value.