514-production-rollout-plan

Plan staged production rollouts for Moose schema, model, or query changes.

3|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/514-labs/agent-skills --skill 514-production-rollout-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 514-production-rollout-plan
Source: https://github.com/514-labs/agent-skills/tree/main/skills/514/production-rollout-plan
Command: npx skills add https://github.com/514-labs/agent-skills --skill 514-production-rollout-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates safe production rollouts for chosen schema, model, or query changes in Moose projects to reduce risk and downtime by planning validation, backfill, cutover, and governance steps.

Core Features & Use Cases

  • Stage-based rollout planning across SETUP, MIGRATION PLANNING, and REVIEW & SHIP to ensure traceable execution.
  • Automated resolution of target deployment and migration artifacts, plus prerequisites, to enable safe deployment.
  • Backfill, validation, and rollback guidance with explicit steps and guardrails to minimize data loss and downtime.
  • Use cases include shipping a schema migration or query optimization with a concrete rollout plan, validation gates, and awareness of downstream dependencies.

Quick Start

Run /production-rollout-plan <project-slug> to generate and review a rollout plan for your chosen change.

Frequently Asked Questions about 514-production-rollout-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a safe production rollout for a ClickHouse schema migration?

Plan a safe production rollout by generating a stage-based plan covering setup, migration planning, and review to enforce validation, backfill, and cutover guardrails. This reduces risk and downtime by flagging destructive schema changes and dependency blockers.

What is the best way to validate migration artifacts before deploying to production?

Validate migration artifacts by checking them against migrations/plan.yaml and remote_state.json. The rollout process enforces compatibility with the migration schema at .moose/migration_schema.json to ensure safe deployment and prevent errors.

How does backfill planning work during a Moose stack production rollout?

Backfill planning works by generating explicit steps and guardrails within the rollout plan to minimize data loss and downtime. It coordinates the cutover process to ensure data integrity when shipping schema or model changes.

Can I use this rollout plan for query optimizations in Moose projects?

Yes, you can use this rollout plan for query optimizations in Moose projects. It resolves the target deployment and produces a concrete plan with validation gates and awareness of downstream dependencies for shipping query changes safely.

What are the limitations when shipping destructive schema changes in Moose?

Limitations arise when shipping destructive schema changes as the rollout plan actively flags them as blockers. It enforces artifact validation against the remote state and migration schema to prevent unsafe deployments and dependency conflicts.