/gaia-release-plan
user-facingWhat it does
/gaia-release-plan generates a staged rollout and release strategy covering scope, deployment strategy selection, staged rollout percentages with observation windows, rollback criteria, success metrics, and a communication plan.
When to use it
- You are preparing to release a new version and need a structured rollout plan.
- You want to define staged rollout percentages (1% canary, 10%, 50%, 100%) with clear abort criteria at each stage.
Prerequisites
- Architecture and sprint status should exist so the plan can reference completed stories and deployment topology.
How to invoke
/gaia-release-planWhat it does step by step
- Define release scope Determines what is included: stories, features, fixes, breaking changes. Assigns a semantic version number.
- Select deployment strategy Chooses blue-green, canary, rolling, or big-bang based on risk profile and infrastructure.
- Plan staged rollout Defines four stages (1%, 10%, 50%, 100%) with observation windows, metrics to monitor, and abort criteria at each stage.
- Define rollback criteria Establishes automatic and manual rollback triggers with procedures.
- Define success metrics Sets measurable technical, business, and operational metrics with comparison baselines.
- Communication plan Defines stakeholder notification timeline, changelog, and user-facing communications.
- Generate artifact Writes the release plan to
.gaia/artifacts/implementation-artifacts/release-plan-{version}.md.
Inputs
| Input | Source | Description |
|---|---|---|
| Architecture document | .gaia/artifacts/planning-artifacts/architecture.md | Provides infrastructure and deployment strategy context. |
| Sprint status | Sprint files | Completed stories to include in the release scope. |
Outputs
| Output | Location | Description |
|---|---|---|
| Release plan | .gaia/artifacts/implementation-artifacts/release-plan-{version}.md | Comprehensive release plan with scope, strategy, rollout schedule, rollback criteria, metrics, and communication plan. |
Example session
> /gaia-release-plan
Defining release scope...
Version: 1.3.0 (minor -- new features, backward compatible)
Stories: E3-S7, E3-S8, E3-S9
Breaking changes: none
Selecting deployment strategy...
Recommended: Canary (gradual traffic shift)
Planning staged rollout...
Stage 1: 1% canary, 30 min observation
Stage 2: 10%, 2 hour observation
Stage 3: 50%, 4 hour observation
Stage 4: 100%, 24 hour observation
Written to .gaia/artifacts/implementation-artifacts/release-plan-1.3.0.mdWhat to run next
/gaia-deploy-- execute the deployment following this plan./gaia-rollback-plan-- create detailed rollback procedures.
Troubleshooting
No completed stories found
The release scope may be empty. Check sprint status or specify stories manually.