mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-15 02:42:45 +08:00
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>
This commit is contained in:
@@ -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.
|
||||
Reference in New Issue
Block a user