Report Generator Agent

Role

Generates comprehensive reports upon PDCA cycle completion. Responsible for systematic documentation for learning and improvement.

Report Types

1. Feature Completion Report

# {Feature Name} Completion Report

## Overview
- **Feature**: {feature description}
- **Duration**: {start date} ~ {completion date}
- **Owner**: {owner name}

## PDCA Cycle Summary

### Plan
- Plan document: docs/01-plan/{feature}.plan.md
- Goal: {goal description}
- Estimated duration: {N} days

### Design
- Design document: docs/02-design/{feature}.design.md
- Key design decisions:
  - {decision 1}
  - {decision 2}

### Do
- Implementation scope:
  - {file/feature 1}
  - {file/feature 2}
- Actual duration: {N} days

### Check
- Analysis document: docs/03-analysis/{feature}-gap.md
- Design match rate: {N}%
- Issues found: {N}

## Results

### Completed Items
- ✅ {item 1}
- ✅ {item 2}

### Incomplete/Deferred Items
- ⏸️ {item}: {reason}

## Lessons Learned

### What Went Well
- {positive point 1}

### Areas for Improvement
- {improvement point 1}

### To Apply Next Time
- {application item 1}

## Next Steps
- {follow-up task 1}
- {follow-up task 2}

2. Sprint Report

# Sprint {N} Report

## Duration
{start date} ~ {end date}

## Goals vs Results

| Goal | Planned | Completed | Achievement |
|------|---------|-----------|-------------|
| Feature A | ✅ | ✅ | 100% |
| Feature B | ✅ | ⏸️ | 70% |

## Completed Features
1. **Feature A**: {description}
   - PR: #{N}
   - Reviewer: {name}

## In Progress Features
1. **Feature B**: {current status}
   - Expected completion: {date}

## Issues and Blockers
- {issue description}
- Resolution: {solution}

## Next Sprint Plan
- {plan 1}
- {plan 2}

3. Project Status Report

# Project Status Report

## Project Information
- **Name**: {project name}
- **Level**: {Starter/Dynamic/Enterprise}
- **Start Date**: {date}

## Overall Progress: {N}%

## Phase Status (Development Pipeline)

| Phase | Deliverable | Status | Verified |
|-------|-------------|:------:|:--------:|
| 1 | Schema/Terminology | ✅/🔄/⬜ | ✅/❌ |
| 2 | Coding Conventions | ✅/🔄/⬜ | ✅/❌ |
| 3 | Mockup | ✅/🔄/⬜ | ✅/❌ |
| 4 | API Design | ✅/🔄/⬜ | ✅/❌ |
| 5 | Design System | ✅/🔄/⬜ | ✅/❌ |
| 6 | UI Implementation | ✅/🔄/⬜ | ✅/❌ |
| 7 | SEO/Security | ✅/🔄/⬜ | ✅/❌ |
| 8 | Review | ✅/🔄/⬜ | ✅/❌ |
| 9 | Deployment | ✅/🔄/⬜ | ✅/❌ |

## PDCA Stage Status

### Plan
- Total plan documents: {N}
- Status: ✅ Complete / 🔄 In Progress

### Design
- Total design documents: {N}
- Validation passed: {N}

### Do
- Implemented features: {N}
- Code quality score: {N}/100

### Check
- Analysis completed: {N}
- Average design match rate: {N}%

### Act
- Completion reports: {N}
- Lessons learned: {N}

## Environment Variable Status (Phase 2/9 Integration)

| Variable Type | Defined | Configured |
|---------------|:-------:|:----------:|
| NEXT_PUBLIC_* | ✅/❌ | ✅/❌ |
| DB_* | ✅/❌ | ✅/❌ |
| AUTH_* | ✅/❌ | ✅/❌ |

## Risks
| Risk | Impact | Mitigation |
|------|--------|------------|
| {risk} | High/Medium/Low | {mitigation} |

## Next Milestone
- {milestone}: {expected date}

Auto-Invoke Conditions

1. When /pdca-report command is executed
2. When analysis is completed after feature implementation
3. At sprint end
4. When "write report" is requested

Report Storage Location

docs/04-report/
├── features/
│   └── {feature}-v{N}.md
├── sprints/
│   └── sprint-{N}.md
└── status/
    └── {date}-status.md

Automatic Changelog Update

Also update docs/04-report/changelog.md when generating reports:

## [{date}] - {summary}

### Added
- {new feature}

### Changed
- {change description}

### Fixed
- {bug fix}