@cloudkinetix/bmad-enhanced
Version:
Cloud-Kinetix enhanced fork of BMAD-METHOD - Breakthrough Method of Agile AI-driven Development with robust versioning and unified validation.
211 lines (153 loc) • 3.82 kB
Markdown
# Semantic Analysis Review Document
**Analysis ID**: {{analysisId}}
**Generated**: {{timestamp}}
**Instructions**: This document is for your review and enhancement of the AI analysis. Your feedback will improve future analyses.
## Quick Agreement Scale
For each section below, indicate your agreement level:
- ✅ **Agree** - Analysis is accurate
- ⚠️ **Partially Agree** - Some corrections needed
- ❌ **Disagree** - Significant issues with analysis
## Dependency Analysis Review
### 1. File Dependencies
**AI's Analysis**: {{fileDependencies.summary}}
**Your Agreement**: [ ] Agree [ ] Partial [ ] Disagree
**Corrections**:
```yaml
# List any files the AI missed or incorrectly identified
missed_files:
-
incorrect_files:
-
```
### 2. Hidden Dependencies
**AI Found**: {{hiddenDependencies.length}} hidden dependencies
{{#each hiddenDependencies}}
- {{title}}: {{summary}}
{{/each}}
**Your Agreement**: [ ] Agree [ ] Partial [ ] Disagree
**Missed Dependencies**:
```yaml
# Describe any dependencies the AI missed
missed:
- description:
components: []
reason:
```
### 3. Risk Assessment
**AI's Risk Level**: {{riskAssessment.level}}
**Reasoning**: {{riskAssessment.reasoning}}
**Your Assessment**: [ ] Too High [ ] Accurate [ ] Too Low
**Reasoning**:
```yaml
# Explain your risk assessment if different
risk_level: # LOW/MEDIUM/HIGH
reasoning: |
additional_risks:
-
```
## Enhanced Wave Planning
### Current Plan Issues
```yaml
# Describe any issues with the proposed wave plan
issues:
- wave:
problem:
impact:
```
### Improved Wave Composition
```yaml
# Propose your preferred wave composition
wave_1:
items: []
reasoning: ""
estimated_duration: ""
wave_2:
items: []
reasoning: ""
estimated_duration: ""
wave_3:
items: []
reasoning: ""
estimated_duration: ""
```
## Additional Context
### Architecture Notes
```yaml
# Provide architectural context the AI should know
architecture:
patterns_used:
-
service_boundaries:
-
critical_components:
-
```
### Business Logic Clarifications
```yaml
# Clarify business rules or logic
business_rules:
- rule:
impact:
components: []
```
### Historical Context
```yaml
# Note past issues or patterns relevant to this work
past_issues:
- description:
when:
resolution:
recurring_patterns:
- pattern:
frequency:
impact:
```
## Feedback for AI Improvement
### What the AI Got Right
```yaml
# Highlight accurate insights
accurate_insights:
-
-
particularly_helpful:
-
```
### What the AI Missed
```yaml
# Note important missed aspects
missed_aspects:
- category: # dependencies/risks/architecture/business_logic
description:
importance: # critical/important/nice_to_have
```
### Suggestions for Better Analysis
```yaml
# How could the AI improve its analysis approach
improvements:
- area: # dependency_detection/risk_assessment/wave_planning
suggestion:
example:
```
## Overall Assessment
### Agreement Summary
- File Dependencies: [ ] High [ ] Medium [ ] Low
- Semantic Dependencies: [ ] High [ ] Medium [ ] Low
- Hidden Dependencies: [ ] High [ ] Medium [ ] Low
- Wave Planning: [ ] High [ ] Medium [ ] Low
- Risk Assessment: [ ] High [ ] Medium [ ] Low
### Would you like to:
- [ ] Proceed with AI's analysis as-is
- [ ] Proceed with your corrections applied
- [ ] Request re-analysis with your feedback
- [ ] Cancel and perform manual analysis
### Final Comments
```yaml
# Any additional feedback or context
comments: |
```
**Thank you for your review!** Your feedback helps improve the AI's analysis capabilities.
To submit this review:
1. Save this file with your changes
2. The system will automatically process your feedback
3. If you requested re-analysis, it will begin immediately