deployment-devops

AWS, Azure, GCP CLIs. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `cloud-tools` work when listed in TEAM.yaml or explicitly requested.

Canonical container workflows: Docker/Compose development plus MCP-style container management patterns.

Plan launch readiness, staged rollouts, production monitoring, rollback, communications, and post-launch validation. Use when the user asks for `/ship`, pre-launch checklists, release readiness, staged rollout plans, feature flags, deployment monitoring, or rollback planning.

Infrastructure and DevOps tooling (Terraform, K8s, Config Mgmt). Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `infra-tools` work when listed in TEAM.yaml or explicitly requested.

Expert application observability: structured logging, correlation IDs, health checks, metrics/SLIs, error tracking, and safe diagnostics without leaking secrets or excess PII. Use when adding logging/monitoring for services, diagnosing production-like failures, defining health/readiness endpoints, or improving operational visibility in Phase 2+ ...

Tmux session management. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `tmux-workspace` work when listed in TEAM.yaml or explicitly requested.

Claude monitoring and usage tracking tools (UV, claude-monitor, claude-usage-cli). Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `monitoring` work when listed in TEAM.yaml or explicitly requested.

Global mise configuration and settings. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `mise-config` work when listed in TEAM.yaml or explicitly requested.