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>

.claude/workflows/cli-templates/prompts/verification/codex-technical.txt

@@ -0,0 +1,59 @@
+Technical feasibility assessment of workflow implementation plan from code quality and execution perspective:
+
+## Required Technical Analysis:
+1. **Implementation Complexity Assessment**
+   - Evaluate code complexity and technical difficulty
+   - Assess required technical skills and expertise levels
+   - Validate implementation approach feasibility
+   - Identify technical challenges and solutions
+
+2. **Technical Dependencies Validation**
+   - Review external library and framework dependencies
+   - Assess version compatibility and dependency conflicts
+   - Evaluate build system and deployment requirements
+   - Identify missing technical prerequisites
+
+3. **Code Structure Assessment**
+   - Evaluate proposed file organization and structure
+   - Assess naming conventions and code organization
+   - Validate integration with existing codebase patterns
+   - Review modularity and separation of concerns
+
+4. **Testing Completeness Evaluation**
+   - Assess test coverage and testing strategy completeness
+   - Evaluate test types and testing approach adequacy
+   - Review integration testing and end-to-end coverage
+   - Identify testing gaps and quality assurance needs
+
+5. **Execution Readiness Verification**
+   - Validate flow_control definitions and execution paths
+   - Assess task context completeness and adequacy
+   - Evaluate target_files specifications and accuracy
+   - Review implementation prerequisites and setup requirements
+
+## Output Requirements:
+### Technical Assessment Report:
+- **Implementation Grade** (A-F): Technical approach quality
+- **Complexity Score** (1-10): Implementation difficulty level
+- **Readiness Level** (1-5): Execution preparation completeness
+- **Quality Rating** (1-10): Code quality and maintainability projection
+
+### Detailed Technical Findings:
+- **Blocking Issues**: Technical problems that prevent implementation
+- **Performance Concerns**: Scalability and performance implications
+- **Quality Improvements**: Code quality and maintainability enhancements
+- **Testing Enhancements**: Testing strategy and coverage improvements
+
+### Implementation Recommendations:
+- **Prerequisites**: Required setup and configuration changes
+- **Best Practices**: Code patterns and conventions to follow
+- **Tool Requirements**: Additional tools or dependencies needed
+- **Refactoring Suggestions**: Code structure and organization improvements
+
+### Risk Mitigation:
+- **Technical Risks**: Implementation complexity and technical debt
+- **Dependency Risks**: External dependencies and compatibility issues
+- **Integration Risks**: Codebase integration and compatibility concerns
+- **Quality Risks**: Code quality and maintainability implications
+
+Focus on technical execution details, code quality concerns, and implementation feasibility. Provide specific, actionable recommendations with clear implementation guidance and priority levels.

.claude/workflows/cli-templates/prompts/verification/cross-validation.txt

@@ -0,0 +1,65 @@
+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.

.claude/workflows/cli-templates/prompts/verification/gemini-strategic.txt

@@ -0,0 +1,52 @@
+Strategic validation of workflow implementation plan from architectural and business perspective:
+
+## Required Strategic Analysis:
+1. **Architectural Soundness Assessment**
+   - Evaluate overall system design coherence
+   - Assess component interaction patterns
+   - Validate architectural decision consistency
+   - Identify potential design conflicts or gaps
+
+2. **Task Decomposition Logic Evaluation**
+   - Review task breakdown methodology and rationale
+   - Assess functional completeness of each task
+   - Evaluate task granularity and scope appropriateness
+   - Identify missing or redundant decomposition elements
+
+3. **Dependency Coherence Analysis**
+   - Map task interdependencies and logical flow
+   - Validate dependency ordering and scheduling
+   - Assess circular dependency risks
+   - Evaluate parallel execution opportunities
+
+4. **Business Alignment Verification**
+   - Validate alignment with stated business objectives
+   - Assess stakeholder requirement coverage
+   - Evaluate success criteria completeness and measurability
+   - Identify business risk and mitigation adequacy
+
+5. **Strategic Risk Identification**
+   - Identify architectural risks and technical debt implications
+   - Assess implementation complexity and resource requirements
+   - Evaluate timeline feasibility and milestone realism
+   - Document potential blockers and escalation scenarios
+
+## Output Requirements:
+### Strategic Assessment Report:
+- **Architecture Grade** (A-F): Overall design quality assessment
+- **Decomposition Grade** (A-F): Task breakdown effectiveness
+- **Risk Level** (Low/Medium/High): Combined implementation risk
+- **Business Alignment Score** (1-10): Requirement satisfaction level
+
+### Detailed Recommendations:
+- **Critical Issues**: Must-fix problems that could cause failure
+- **Improvement Opportunities**: Non-blocking enhancements
+- **Alternative Approaches**: Strategic alternatives worth considering
+- **Resource Implications**: Staffing and timeline considerations
+
+### Action Items:
+- **Immediate**: Changes needed before implementation starts
+- **Short-term**: Improvements for early phases
+- **Long-term**: Strategic enhancements for future iterations
+
+Focus on high-level strategic concerns, business alignment, and long-term architectural implications. Provide actionable recommendations with clear rationale and priority levels.