deploylisted

# /deploy — Stage-Gated Deployment Orchestrator Walk a deployment through 5 phases with explicit gates between them. Ensures no env var, secret, migration, or config is missed. ## Variant router — load before Phase 1 Before reading further, identify the project's tooling and load the matching reference deep-dives. Each reference is opinionated + concrete (real commands, real failure modes, real fixes). | If the project uses... | Load before reaching... | |---|---| | ArgoCD as GitOps controller | `references/gitops-argocd.md` → Phase 3 | | Flux v2 as GitOps controller | `references/gitops-flux.md` → Phase 3 | | External Secrets Operator (ESO) | `references/secrets-externalsecrets.md` → Phase 1.4 | | Sealed-secrets (Bitnami) | `references/secrets-sealedsecrets.md` → Phase 1.4 | | Any DB schema in the deploy scope | `references/migrations-patterns.md` → Phase 1.5 | | Always (for the smoke + sign-off matrix) | `references/health-probes.md` → Phase 4 | **You can scope check** with `Grep` on the gitops repo: - ArgoCD: `Grep "kind: Application" deploy/` finds Application CRs. - Flux: `Grep "kind: Kustomization" deploy/` finds Flux Kustomizations. - ESO: `Grep "kind: ExternalSecret" deploy/`. - Sealed: `Grep "kind: SealedSecret" deploy/`. ## When to split: `/deploy-preflight` vs `/deploy` - `/deploy-preflight <env>` — read-only Phase 1 only. No env risk. Use when you want to know "what would deploy break?" without committing to a deploy. - `/deploy <env>` — full 5-phase or