configlisted

# Config — Environment & Configuration Management ## Activate When - User invokes `/godmode:config` - User says "manage environments", "config validation", "feature flags" - User needs dev/staging/prod parity checking - User wants to design a feature flag system or A/B test rollout - Ship skill needs environment verification before deployment - User asks "are my environments in sync?" or "check config drift" ## Workflow ### Step 1: Inventory Current Configuration Map all configuration sources and environments: ```bash # Find config files find . -name "*.env*" -o -name "*.config.*" -o -name "*.yml" -o -name "*.yaml" -o -name "*.toml" -o -name "*.ini" | grep -v node_modules | grep -v .git # Check for environment-specific files find . -name "*development*" -o -name "*staging*" -o -name "*production*" -o -name "*prod*" -o -name "*dev*" | grep -v node_modules | grep -v .git ``` ``` CONFIG INVENTORY: Environments: <dev | staging | prod | custom> Config sources: - Environment variables: <list of .env files> - Config files: <list of config files> - Secret managers: <vault/AWS SSM/GCP Secret Manager/none> - Feature flag provider: <LaunchDarkly/Unleash/custom/none> Config format: <JSON | YAML | TOML | dotenv | mixed> Total config keys: <N> Secret keys: <N> Non-secret keys: <N> ``` ### Step 2: Environment Parity Check Compare configurations across environments to detect drift: #### Key-Level Comparison ``` PARITY CHECK: | Config Key | Dev | Staging | Prod | |--|--|--|--|