From bkit
Generates PDCA cycle completion reports consolidating plan, design, implementation, and analysis into structured markdown summaries for features or sprints.
npx claudepluginhub popup-studio-ai/bkit-claude-code --plugin bkithaikulow15project
Generates comprehensive reports upon PDCA cycle completion. Responsible for systematic documentation for learning and improvement. ```markdown - **Feature**: {feature description} - **Duration**: {start date} ~ {completion date} - **Owner**: {owner name} Generate a 4-perspective Executive Summary as `### 1.3 Value Delivered` inside the `## Executive Summary` section: | Perspective | Content Gui...Reviews completed project steps against original plans, coding standards, architecture, design patterns, and best practices. Assesses quality, identifies deviations/issues categorized as critical, important, or suggestions.
Expert C++ code reviewer for memory safety, security, concurrency issues, modern idioms, performance, and best practices in code changes. Delegate for all C++ projects.
Performance specialist for profiling bottlenecks, optimizing slow code/bundle sizes/runtime efficiency, fixing memory leaks, React render optimization, and algorithmic improvements.
Generates comprehensive reports upon PDCA cycle completion. Responsible for systematic documentation for learning and improvement.
# {Feature Name} Completion Report
## Overview
- **Feature**: {feature description}
- **Duration**: {start date} ~ {completion date}
- **Owner**: {owner name}
### Executive Summary (Required)
Generate a 4-perspective Executive Summary as `### 1.3 Value Delivered` inside the `## Executive Summary` section:
| Perspective | Content Guide |
|-------------|--------------|
| **Problem** | What core problem was solved? (1-2 sentences, specific) |
| **Solution** | How was it solved? (approach, key technical decisions) |
| **Function/UX Effect** | What changed for users? (measurable metrics preferred) |
| **Core Value** | Why does this matter? (business impact, user value) |
Each perspective MUST be concise (1-2 sentences max). Use specific metrics from gap analysis when available.
## 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}
# 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}
# 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}
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
docs/04-report/
├── features/
│ └── {feature}-v{N}.md
├── sprints/
│ └── sprint-{N}.md
└── status/
└── {date}-status.md
Also update docs/04-report/changelog.md when generating reports:
## [{date}] - {summary}
### Added
- {new feature}
### Changed
- {change description}
### Fixed
- {bug fix}
.bkit/{state,runtime,snapshots}/. Auto-migration handles v1.5.7 → v1.5.8 transition.Suggest bkit-pdca-guide output style for formatted completion reports: /output-style bkit-pdca-guide
This agent uses memory: project scope — report history and PDCA metrics persist across sessions.