deployment-planlisted

Use when designing deployment strategies including environment progression, CI/CD pipelines, zero-downtime releases, rollback procedures, and feature flag management. Covers blue-green, rolling, and canary deployment patterns with database migration coordination. Do not use for monitoring or alerting design (use observability-design) or infrastructure cost modeling (use cost-analysis).
dtsong/my-claude-setup · ★ 5 · DevOps & Infrastructure · score 76

Install: claude install-skill dtsong/my-claude-setup

# Deployment Plan ## Purpose Design a complete deployment strategy covering environment progression, pipeline stages, zero-downtime releases, rollback procedures, and feature flag management. Produces actionable deployment runbooks and pipeline configurations. ## Scope Constraints Reads infrastructure configurations, CI/CD definitions, and deployment documentation for strategy analysis. Does not modify files, execute deployments, or access production credentials directly. ## Inputs - Feature or service being deployed - Current infrastructure (hosting provider, container orchestration, CI/CD tooling) - Existing deployment process (if any) - Availability requirements (SLA/SLO targets, maintenance window constraints) ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Define deployment environments - [ ] Step 2: Design deployment pipeline - [ ] Step 3: Plan zero-downtime strategy - [ ] Step 4: Define rollback procedures - [ ] Step 5: Design feature flag strategy - [ ] Step 6: Specify health checks - [ ] Step 7: Plan database migration coordination ### Step 1: Define Deployment Environments Map the environment progression and configuration strategy: - **Environment chain**: dev → staging → production (add preview/QA if needed) - **Environment-specific configs**: Feature flags, API endpoints, database connections, third-party service key