gabrielmoreira Release Launch Readiness
Core Workflow
- Identify what is launching, who is affected, release surface, risk level, dependencies, timing, and rollback constraints.
- Separate deploy, release, and launch. Code can be deployed before a feature is released or marketed.
- Define readiness gates: QA, security/privacy, accessibility, performance, analytics, documentation, support, legal/compliance, billing, and communications.
- Plan rollout: internal, beta, cohort, percentage, region, platform, feature flag, waitlist, or full launch.
- Prepare rollback or mitigation: feature flag off, config rollback, build rollback, data migration plan, hotfix, support script, and owner.
- Set monitoring and response: dashboards, alerts, logs, health metrics, business metrics, incident channel, escalation, and decision owner.
- Run post-launch review with outcomes, incidents, learnings, and follow-up actions.
Freshness Rule
Verify current deployment platform, marketplace, app-store, payment, compliance, and incident-management requirements before giving tactical release guidance. Release operations depend heavily on the actual stack and platform rules.
Deliverable Shape
For release work, provide:
- Launch scope and risk profile
- Readiness checklist
- Rollout plan
- Rollback/mitigation plan
- Monitoring and support plan
- Communication plan
- Post-launch review criteria
References
- Read
references/release-launch-checklist.mdwhen planning or auditing a release or launch.