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 2026-10-28 11:20:18 +09:00
commit 964a841de1
3978 files changed
+58013356

No files matched your search

@@ -0,0 +1,169 @@
---
name: hmcmkit-templates
classification: workflow
classification-reason: Process automation persists regardless of model advancement
deprecation-risk: none
description: |
PDCA document templates — Plan, Design, Analysis, Report with consistent structure.
Triggers: template, plan document, design template, 템플릿, 문서 양식.
user-invocable: false
---
# hmcmkit Document Templates
> Use these templates when generating PDCA documents.
## Available Templates
| Template | Path | Purpose |
|----------|------|---------|
| Plan | `${HMCMKIT_PLUGIN_ROOT}/templates/plan.template.md` | Feature planning |
| Design | `${HMCMKIT_PLUGIN_ROOT}/templates/design.template.md` | Technical design |
| Analysis | `${HMCMKIT_PLUGIN_ROOT}/templates/analysis.template.md` | Gap analysis |
| Report | `${HMCMKIT_PLUGIN_ROOT}/templates/report.template.md` | Completion report |
| Index | `${HMCMKIT_PLUGIN_ROOT}/templates/_INDEX.template.md` | Document index |
| CLAUDE | `${HMCMKIT_PLUGIN_ROOT}/templates/agents.template.md` | agents.md template |
## Template Usage
### Plan Template
For **P**lan phase - feature planning before design.
Key sections:
- Overview & Purpose
- Scope (In/Out)
- Requirements (Functional/Non-Functional)
- Success Criteria
- Risks & Mitigation
### Design Template
For **D**o phase - technical design before implementation.
Key sections:
- Architecture (diagrams, data flow)
- Data Model (entities, relationships)
- API Specification (endpoints, request/response)
- UI/UX Design (layouts, components)
- Error Handling
- Security Considerations
- Test Plan
- Implementation Guide
### Analysis Template
For **C**heck phase - gap analysis between design and implementation.
Key sections:
- Design vs Implementation comparison
- Missing features
- Inconsistencies
- Quality metrics
- Recommendations
### Report Template
For **A**ct phase - completion report and lessons learned.
Key sections:
- Summary of completed work
- Metrics (LOC, test coverage, etc.)
- Issues encountered
- Lessons learned
- Future improvements
## Document Output Paths
```
docs/
├── 01-plan/
│ └── features/
│ └── {feature}.plan.md
├── 02-design/
│ └── features/
│ └── {feature}.design.md
├── 03-analysis/
│ └── features/
│ └── {feature}.analysis.md
└── 04-report/
└── features/
└── {feature}.report.md
```
## Variable Substitution
Templates use `{variable}` syntax:
- `{feature}`: Feature name
- `{date}`: Creation date (YYYY-MM-DD)
- `{author}`: Document author
## Pipeline Templates
Additional templates for Development Pipeline phases:
- `${HMCMKIT_PLUGIN_ROOT}/templates/pipeline/` directory
---
## Document Standards
### File Naming Rules
```
{number}_{english_name}.md # 01_system_architecture.md
{number}-{english_name}.md # 01-system-architecture.md
{feature}.{type}.md # login.design.md
```
### Common Header
All documents should include:
```markdown
# {Document Title}
> **Summary**: {One-line description}
>
> **Author**: {Name}
> **Created**: {YYYY-MM-DD}
> **Last Modified**: {YYYY-MM-DD}
> **Status**: {Draft | Review | Approved | Deprecated}
---
```
### Version Control
Track changes within documents:
```markdown
## Version History
| Version | Date | Changes | Author |
|---------|------|---------|--------|
| 1.0 | 2024-12-01 | Initial draft | Kay |
| 1.1 | 2024-12-05 | Added API spec | Kay |
```
### Cross-References
Link related documents:
```markdown
## Related Documents
- Plan: [login.plan.md](../01-plan/features/login.plan.md)
- Design: [login.design.md](../02-design/features/login.design.md)
- Analysis: [login.analysis.md](../03-analysis/features/login.analysis.md)
```
### Status Tracking
Use _INDEX.md in each folder:
| Status | Meaning | AI Agent Behavior |
|--------|---------|-----------------|
| ✅ Approved | Use as reference | Follow as-is |
| 🔄 In Progress | Being written | Notify of changes |
| ⏸️ On Hold | Temporarily paused | Request confirmation |
| ❌ Deprecated | No longer valid | Ignore |
### Conflict Resolution
- **Code vs Design mismatch**: Code is truth, suggest document update
- **Multiple versions**: Reference only the latest version