deployment-chart-managelisted

# Deployment Chart Manage: $ARGUMENTS Provision or reconcile the Helm application chart for `$ARGUMENTS`, built on the bjw-s `common` library. This skill **orchestrates**; the heavy work is done by three dispatched agents, and their results flow back here so you drive the gates and own the chart on disk. Governed by `spec/project/bjw-s-common-chart-deployment/` (chart structure and the README manual-steps contract) and `spec/project/kubernetes-deployment-best-practices/` (the security-and-scalability bar, with network policies and the security context as mandatory pillars). Don't restate those specs; the dispatched agents read them. ## Why this is a skill, not an agent - **Orchestrator that chains other capabilities:** the flow dispatches `deployment-change-analyzer`, `bjw-common-deployment-generator`, and `deployment-bestpractices-reviewer`; the skill-orchestrates pattern (per `skill-vs-agent`) defaults the orchestrator to skill form. - **Mid-flow gating lives in the conversation:** confirming the provisioning inputs (image, exposure, ingress host, secrets, storage), approving *which* drift gaps to apply during reconcile, and deciding whether a best-practice finding blocks are per-turn user-visible gates an agent's fire-and-forget shape would lose. - **Owns a persistent on-disk artifact:** the chart files and the README manual-steps section are the deliverable; skills own persistent state. - Counter-dimension considered: each phase (detect, generate, audit) is a self-con