원클릭으로
deployment
// Enable and operate the Deployment feature (ops/deploy conventions + deploy scripts) for multi-environment delivery.
// Enable and operate the Deployment feature (ops/deploy conventions + deploy scripts) for multi-environment delivery.
Treat convex/schema.ts as the database Single Source of Truth, initialize Convex scaffolding, regenerate docs/context/db/schema.json and docs/context/convex/functions.json, and verify the repository stays aligned with Convex mode.
Mirror schema changes from a real database (SSOT) into repo artifacts (prisma/schema.prisma + db/schema/tables.json) and refresh LLM context (docs/context/db/schema.json).
Apply schema changes from repo SSOT (prisma/schema.prisma) to a target DB via Prisma migrations, with diff preview + approval gate; then refresh LLM context (docs/context/db/schema.json).
Plan/apply/verify cloud environment config and secret references using env contract + policy/inventory routing; detect drift, rotate secrets, and decommission environments with approval gates. Use for staging/prod deployments and maintenance.
Maintain env contract SSOT (env/contract.yaml), validate env/values + env/secrets refs coverage, and generate env/.env.example + docs/context/env/*. Use when adding/renaming/deprecating config keys.
Bootstrap, diagnose (doctor), and reconcile local dev environment from env contract/values/secret refs; generate .env.local and redacted docs/context/env/effective-*. Use when local env is broken or needs syncing.
| name | deployment |
| description | Enable and operate the Deployment feature (ops/deploy conventions + deploy scripts) for multi-environment delivery. |
Standardize how the repo describes and executes deployments across environments (dev/staging/prod) in an LLM-friendly, auditable way.
The repo keeps deployment artifacts under ops/deploy/ and exposes a small set of controller scripts under .ai/.
When enabled, this feature materializes:
ops/deploy/**
ops/deploy/environments/*.yamlops/deploy/k8s/manifests/deployment.template.yamlops/deploy/scripts/healthcheck.mjsops/deploy/handbook/** (runbooks, rollback procedure)Controller scripts (provided by the template SSOT):
node .ai/skills/features/deployment/scripts/ctl-deploy.mjs — deployment configuration managementnode .ai/skills/features/deployment/scripts/rollback.mjs — rollback entry point (human-run).ai/skills/features/deployment/templates/
into the repo root.node .ai/skills/features/deployment/scripts/ctl-deploy.mjs init
node .ai/skills/features/deployment/scripts/ctl-deploy.mjs verify
Optional (recommended for LLM routing): record the flag in project state:
node .ai/scripts/ctl-project-state.mjs init
node .ai/scripts/ctl-project-state.mjs set features.deployment true
ops/deploy/handbook/.node .ai/skills/features/deployment/scripts/ctl-deploy.mjs verify
ops/deploy/**.ops/deploy/** and related controller scripts).