- 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>
Deploy feature to target environment (dev/staging/prod) with level-based strategy
3.0.0
workflow
hmcmkit:infra-architect
do
deploy
/pdca deploy
배포
デプロイ
部署
Deploy Skill
Deploy code to target environment with automated CI/CD pipeline generation.
Strategy adapts based on project level (Starter/Dynamic/Enterprise).
Usage
/pdca deploy {feature}# Deploy to default env (dev)
/pdca deploy {feature} --env dev # Deploy to DEV
/pdca deploy {feature} --env staging # Deploy to STAGING (requires DEV 90%+)
/pdca deploy {feature} --env prod # Deploy to PROD (requires STAGING 95%+ & Human Approval)
/pdca deploy status # Show deploy state machine status
Level-Based Strategy
Level
Strategy
Environments
Tools
Starter
Guide only
dev
GitHub Pages, Netlify, Vercel
Dynamic
Docker + GHA
dev, staging
Docker Compose, GitHub Actions
Enterprise
6-Layer CI/CD
dev, staging, prod
Terraform, EKS, ArgoCD, Canary
Deploy Flow
/pdca deploy feature --env dev
│
▼
① Level Detection (Starter/Dynamic/Enterprise)
│
▼
② Generate CI/CD Files (if not exist)
├── .github/workflows/deploy.yml
├── Dockerfile (Dynamic/Enterprise)
├── docker-compose.yml (DEV)
├── k8s/ manifests (Enterprise)
└── terraform/ (Enterprise)
│
▼
③ Deploy State Machine Transition
init → dev → verify(90%) → staging → verify(95%) → approval → prod(canary) → complete
│
▼
④ Return to PDCA Check phase