メニュー
Deploy feature to target environment (dev/staging/prod) with level-based strategy. Triggers: deploy, /pdca deploy
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/popup-studio-ai/bkit-claude-code --skill deployコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
| name | deploy |
| classification | workflow |
| classification-reason | Deployment execution independent of model capability |
| deprecation-risk | none |
| effort | high |
| description | Deploy feature to target environment (dev/staging/prod) with level-based strategy. Triggers: deploy, /pdca deploy |
| argument-hint | [feature] [--env dev|staging|prod] |
| user-invocable | true |
| agents | {"orchestrator":"bkit:infra-architect"} |
| allowed-tools | ["Read","Write","Edit","Glob","Grep","Bash"] |
| pdca-phase | do |
| task-template | [Deploy] {feature} |
Deploy code to target environment with automated CI/CD pipeline generation. Strategy adapts based on project level (Starter/Dynamic/Enterprise).
/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 | 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 |
/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
| Gate | Condition | Action |
|---|---|---|
| DEV → STAGING | Match Rate ≥ 90% | Auto-promote |
| STAGING → PROD | Match Rate ≥ 95% + Human Approval | Require /pdca deploy --env prod |
| PROD Canary | Error rate < threshold | Auto-rollout 10% → 25% → 50% → 100% |
.github/workflows/deploy.yml — Docker build + push + deployDockerfile — Multi-stage builddocker-compose.yml — DEV environment.env.example — Environment variables templateinfra/terraform/ — AWS infrastructureinfra/k8s/ — Kubernetes manifestsinfra/argocd/ — ArgoCD Application + Helm/pdca deploy rollback {feature} # Rollback current deploy
/pdca deploy rollback {feature} --env prod # Rollback specific environment
Rollback triggers:
/pdca deploy rollback commandself-healing agent exhausts its 5-iteration auto-fix budget without restoring SLO, it triggers /pdca deploy rollback as final remediation (see Self-Healing Integration below).Rollback resets deploy state machine to idle and restores previous version.
The self-healing agent (linked-from-skills: deploy) closes the deploy ⇄ recovery loop:
| Stage | Trigger | Action |
|---|---|---|
| Detect | Sentry/Slack error pattern matches deploy window | self-healing agent activated via 8-lang triggers ("자동 수정", "auto fix", etc.) |
| Diagnose | 4-Layer Living Context loaded (Scenarios + Invariants + Impact + Incidents) | Identify deploy-introduced regression |
| Auto-fix | Spawn code-analyzer + gap-detector via Task tool | Up to 5 iteration cycles with scenario runner verification |
| Verify | Re-run feature scenarios | Pass → auto PR; Fail → escalate |
| Escalate | Iteration budget exhausted or critical invariant violated | Trigger /pdca deploy rollback + alert human on-call |
Invocation paths:
/pdca deploy rollback first checks for active self-healing session and aborts to wait for it; user can force-bypass with --force-rollbackThe self-healing → deploy contract is mediated by lib/audit/audit-logger.js ACTION_TYPES (rollback_executed, agent_completed, gate_failed) so all transitions remain audit-trail compliant.
| Event | When | Hook |
|---|---|---|
deploy-start | Deploy initiated | Pre-validation |
deploy-complete | Deploy successful | Post-notification |
deploy-failed | Deploy failed | Error handling + rollback suggestion |