Skill

deploy

Deploys features to dev/staging/prod environments using level-based strategies: Starter (Vercel/Netlify guides), Dynamic (Docker/GitHub Actions), Enterprise (Terraform/Kubernetes/ArgoCD). Includes rollback and gates.

Docker

Docker Compose

Install

npx claudepluginhub popup-studio-ai/bkit-claude-code --plugin bkit

Tool Access

This skill is limited to using the following tools:

ReadWriteEditGlobGrepBash

Preview

> Deploy code to target environment with automated CI/CD pipeline generation.

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Stars513

Forks130

Last CommitApr 8, 2026

Actions

View Source View Plugin View on GitHub View README

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

Environment Promotion Gates

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%

Generated Files

Starter

Deployment guide document only

Dynamic

.github/workflows/deploy.yml — Docker build + push + deploy
Dockerfile — Multi-stage build
docker-compose.yml — DEV environment
.env.example — Environment variables template

Enterprise (additional)

infra/terraform/ — AWS infrastructure
infra/k8s/ — Kubernetes manifests
infra/argocd/ — ArgoCD Application + Helm
Security scan steps in CI/CD

Rollback

/pdca deploy rollback {feature}              # Rollback current deploy
/pdca deploy rollback {feature} --env prod   # Rollback specific environment

Rollback triggers:

Manual: /pdca deploy rollback command
Auto: Error rate spike detected by ops-metrics (> 5% threshold)
Canary fail: Argo Rollouts auto-rollback on metrics failure

Rollback resets deploy state machine to idle and restores previous version.

Hook Events

Event	When	Hook
`deploy-start`	Deploy initiated	Pre-validation
`deploy-complete`	Deploy successful	Post-notification
`deploy-failed`	Deploy failed	Error handling + rollback suggestion