514-production-rollout-plan
Production Rollout Planning
Run through three stages sequentially: SETUP -> MIGRATION PLANNING -> REVIEW AND SHIP.
If the user provided a project slug as an argument, use it to skip the project selection prompt in Stage 1.
Command safety
Commands fall into three categories:
Guardrailed read-only: 514 agent auth whoami, 514 agent project list, 514 agent deployment list, 514 agent table list, 514 agent materialized-view list, 514 agent sql-resource list, 514 deployment list, 514 env list, 514 env get, git branch --show-current, git status --short, git diff --name-only, gh pr view, moose ls
Raw ClickHouse (require user approval): Any 514 clickhouse query invocation used to inspect current production state or define validation SQL.
Before running any 514 clickhouse query command, use AskUserQuestion to show the user the exact command or SQL and get explicit approval.
Stage 1 — SETUP
More from 514-labs/agent-skills
clickhouse-best-practices-ts-py
Use when designing, implementing, reviewing, or optimizing MooseStack data models, ClickHouse schemas, queries, indexes, materialized views, or ingestion configs — including during greenfield authoring when schema-design or performance choices need guidance. When invoked, pick the 1-2 rules directly relevant to the immediate decision and apply them inline while you continue to write code. Do NOT pause to read six rule files and emit a "Rules Checked / Findings" audit template unless the user explicitly asks for a formal review or audit.
19514-cli
>
5514-debug
>
4514-perf-optimize
>
4moose-basics
>
3moosestack-clickhouse-best-practices
MUST USE when reviewing MooseStack data models, ClickHouse schemas, queries, or configurations. Contains 28 rules with MooseStack TypeScript/Python examples. Always read relevant rule files and cite specific rules in responses.
3