# Generation Report Template

This template provides a standardized structure for generation reports. The `/report` command uses this as a foundation, customizing sections based on actual data.

---

## Report Metadata

**Report Type:** [Summary / Detailed / Executive / Technical]
**Generated:** [ISO 8601 timestamp]
**Report Version:** 1.0
**Generated By:** Claude Code Infinite Loop Report Utility

---

## Section 1: Executive Summary

### Purpose
Provide at-a-glance understanding of generation results for decision-makers.

### Contents
- **Key Findings** - Top 3-5 most important discoveries
- **Overall Assessment** - Quality rating and compliance status
- **Recommendation** - Approve/conditional/revise decision
- **Critical Statistics** - Essential numbers (total, pass rate, quality avg)

### Chain-of-Thought Application
This section answers: "Should I accept these results?" by synthesizing all findings into a clear decision with supporting rationale.

---

## Section 2: Quantitative Analysis

### Purpose
Present objective, measurable data about generation performance.

### Contents
- **Completion Metrics** - How many, success rate, time per iteration
- **Quality Metrics** - Test pass rate, quality scores, distribution
- **Diversity Metrics** - Theme count, distribution, duplication rate
- **Efficiency Metrics** - Speed, storage, resource utilization
- **Trend Metrics** - Changes over time

### Chain-of-Thought Application
This section answers: "What are the objective facts?" by systematically measuring all quantifiable aspects.

**Reasoning Template:**
```
1. Define metric - What are we measuring and why?
2. Collect data - Where does the measurement come from?
3. Calculate value - How is the metric computed?
4. Compare to benchmark - Is this good, acceptable, or poor?
5. Interpret meaning - What does this tell us?
```

---

## Section 3: Qualitative Assessment

### Purpose
Evaluate non-numeric qualities like creativity, usability, and coherence.

### Contents
- **Content Quality**
  - Creativity - Innovation and originality
  - Technical Quality - Correctness and professionalism
  - Usability Quality - User-facing clarity and polish
- **Pattern Quality**
  - Theme Coherence - How well themes are executed
  - Structural Consistency - Adherence to patterns

### Chain-of-Thought Application
This section answers: "What qualities can't be measured numerically?" by systematically assessing subjective dimensions.

**Reasoning Template:**
```
1. Define quality dimension - What aspect of quality?
2. Establish criteria - What makes this dimension good/bad?
3. Examine examples - Review representative samples
4. Identify patterns - What themes emerge?
5. Assess overall - Rate this dimension
6. Provide evidence - Support rating with examples
```

---

## Section 4: Comparative Analysis

### Purpose
Contextualize performance against specifications, history, and benchmarks.

### Contents
- **Specification Compliance** - Requirement by requirement comparison
- **Historical Comparison** - How this compares to previous generations
- **Benchmark Comparison** - Industry standards or best practices

### Chain-of-Thought Application
This section answers: "How do results compare to expectations and standards?" by systematic comparison.

**Reasoning Template:**
```
1. Identify comparison target - Spec, history, or benchmark?
2. Extract comparison criteria - What should match?
3. Measure actual vs expected - What's the gap?
4. Calculate compliance percentage - How close to target?
5. Identify deviations - Where are the gaps?
6. Explain deviations - Why did gaps occur?
```

---

## Section 5: Issues and Risks

### Purpose
Identify problems, categorize by severity, and flag risks.

### Contents
- **Critical Issues** - Block usage, require immediate action
- **Moderate Issues** - Degrade quality, address soon
- **Minor Issues** - Enhancement opportunities
- **Risk Assessment** - Potential future problems

### Chain-of-Thought Application
This section answers: "What could go wrong?" by systematically identifying and categorizing concerns.

**Reasoning Template:**
```
1. Scan for problems - What issues are present?
2. Assess severity - How bad is each issue?
3. Determine impact - What are the consequences?
4. Trace root cause - Why did this occur?
5. Categorize by priority - Critical/moderate/minor?
6. Propose remediation - How to fix?
7. Identify risks - What future problems might arise?
```

---

## Section 6: Insights and Recommendations

### Purpose
Synthesize findings into actionable guidance.

### Contents
- **Key Insights**
  - Success Factors - What worked well and why
  - Improvement Opportunities - Where to focus efforts
- **Recommendations**
  - Immediate Actions - Do now (high priority, high impact)
  - Short-Term Improvements - Do soon (medium priority)
  - Long-Term Enhancements - Plan for (low priority, high value)
  - Specification Refinements - How to improve the spec

### Chain-of-Thought Application
This section answers: "What should I do with these findings?" by reasoning from data to actionable steps.

**Reasoning Template:**
```
1. Review all findings - What did we learn?
2. Identify patterns - What themes emerge?
3. Determine causation - What caused success/failure?
4. Extract principles - What general insights apply?
5. Prioritize actions - What matters most?
6. Define steps - How to implement?
7. Estimate impact - What will improve?
8. Set timeline - When to act?
```

---

## Section 7: Appendices

### Purpose
Provide supporting details and transparency about methodology.

### Contents
- **Appendix A: Detailed Test Results** - Full test output
- **Appendix B: Analysis Data** - Complete analysis results
- **Appendix C: File Inventory** - List of all generated files
- **Appendix D: Methodology** - How data was collected and analyzed

### Chain-of-Thought Application
This section answers: "How were these conclusions reached?" by documenting the complete reasoning process.

---

## Chain-of-Thought Principles Applied Throughout

### 1. Explicit Reasoning
Every conclusion includes the reasoning chain that led to it.

**Example:**
- ❌ Poor: "Quality is good."
- ✅ Good: "Quality is good (average score 85/100) because completeness (92%) and technical correctness (88%) both exceed targets (80%), though uniqueness (78%) is slightly below the excellent threshold (85%)."

### 2. Step-by-Step Thinking
Complex assessments are broken into logical steps.

**Example:**
- ❌ Poor: "Iterations need improvement."
- ✅ Good: "Step 1: Test results show 15/20 iterations passed. Step 2: Failed iterations all missing interactive controls. Step 3: Root cause is vague spec guidance on interactivity. Step 4: Recommendation: Add explicit interaction requirements to spec section 4.3."

### 3. Transparent Criteria
Decision criteria are made explicit, not implicit.

**Example:**
- ❌ Poor: "This iteration is excellent."
- ✅ Good: "This iteration is excellent because it scores: Completeness 100% (all 5 required sections present), Technical Correctness 95% (valid HTML, no errors), Spec Compliance 98% (meets all requirements), Uniqueness 90% (novel approach), Innovation 95% (creative technique). Composite score: 94/100, exceeding the 90+ threshold for 'excellent'."

### 4. Evidence-Based
Claims are supported with specific evidence.

**Example:**
- ❌ Poor: "Quality is declining."
- ✅ Good: "Quality is declining: Wave 1 average was 88/100, Wave 2 was 82/100, Wave 3 was 76/100, showing a -6 point decline per wave. This suggests context degradation or specification drift."

### 5. Actionable Guidance
Recommendations are specific and implementable.

**Example:**
- ❌ Poor: "Improve uniqueness."
- ✅ Good: "Improve uniqueness by: 1) Adding section 5.2 to spec defining 12 distinct visualization types. 2) Assigning each sub-agent a specific type from the list. 3) Validating post-generation that no two iterations use the same type. This should increase uniqueness scores from 78% to target of 85%+."

---

## Usage Instructions

### For Report Command
1. Load this template
2. Replace bracketed placeholders with actual data
3. Execute reasoning templates for each section
4. Customize based on report type (summary omits some sections, detailed includes all)

### For Manual Use
1. Use as a checklist when creating reports
2. Follow reasoning templates to ensure thoroughness
3. Apply chain-of-thought principles consistently
4. Adapt sections to specific context

### For Quality Assurance
1. Review generated reports against this template
2. Verify all sections are present (for detailed reports)
3. Check that reasoning chains are explicit
4. Ensure recommendations are actionable

---

**Template Version:** 1.0
**Last Updated:** 2025-10-10
**Maintained By:** Infinite Loop Variant 2 Project
