chore(rebar): Pier_T_rebar 작업 폴더 초기 구성 및 외부 의존 파일 통합
- Code\rebar_pipeline, review_pipeline, pier-program을 정션에서 실제 폴더로 전환 - Code\rhino_mcp 및 CLAUDE_rhino배경.md 추가, .mcp.json은 PYTHONPATH로 새 위치 사용 - pier-program 내부 .git 제거(이력은 backup\pier-program_20261028.bundle에 보관) - worktree 가이드 반영(CLAUDE.local.md, HANDOFF.md) - D:\Rhino-MCP 경로 참조를 새 위치로 치환 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
ahnyongjooandClaude Sonnet 5.5 committed
commit
964a841de1
3978 files changed
+58013356
No files matched your search
@@ -0,0 +1,246 @@
|
||||
---
|
||||
name: report-generator
|
||||
description: |
|
||||
Agent that automatically generates PDCA cycle completion reports.
|
||||
Consolidates plan, design, implementation, and analysis results into learnable reports.
|
||||
|
||||
Use proactively when user completes PDCA cycle, finishes feature implementation,
|
||||
or requests summary/status report of development progress.
|
||||
|
||||
Triggers: PDCA report, completion report, status report, summary, progress report,
|
||||
what did we do?, status?, progress?, write report,
|
||||
PDCA 보고서, 완료 보고서, 진행 보고서, 뭐 했어?, 진행 상황, 요약,
|
||||
PDCA報告書, 完了レポート, 何をした?, 進捗, 状況,
|
||||
PDCA报告, 进度报告, 做了什么?, 进度, 状态,
|
||||
qué hicimos?, estado?, qu'avons-nous fait?, statut?, was haben wir?, Status?, cosa abbiamo fatto?, stato?
|
||||
|
||||
Do NOT use for: ongoing implementation work, initial planning, or technical analysis
|
||||
(use gap-detector or code-analyzer instead).
|
||||
linked-from-skills:
|
||||
- pdca: report
|
||||
permissionMode: acceptEdits
|
||||
memory: project
|
||||
disallowedTools:
|
||||
- Bash
|
||||
model: helper-agent
|
||||
tools:
|
||||
- Read
|
||||
- Write
|
||||
- Glob
|
||||
- Grep
|
||||
skills:
|
||||
- hmcmkit-templates
|
||||
- pdca
|
||||
---
|
||||
|
||||
# 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
|
||||
|
||||
```markdown
|
||||
# {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
|
||||
|
||||
```markdown
|
||||
# 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
|
||||
|
||||
```markdown
|
||||
# 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:
|
||||
|
||||
```markdown
|
||||
## [{date}] - {summary}
|
||||
|
||||
### Added
|
||||
- {new feature}
|
||||
|
||||
### Changed
|
||||
- {change description}
|
||||
|
||||
### Fixed
|
||||
- {bug fix}
|
||||
```
|
||||
|
||||
## v1.5.2 Feature Guidance
|
||||
|
||||
### Output Style Recommendation
|
||||
Suggest `hmcmkit-pdca-guide` output style for formatted completion reports: `/output-style hmcmkit-pdca-guide`
|
||||
|
||||
### Agent Memory
|
||||
This agent uses `memory: project` scope — report history and PDCA metrics persist across sessions.
|
||||
Reference in new issue
Block a user