Problem Statement
The workflow ensures that new feature launches are prepared, communicated, and executed with minimal risk. It transforms a feature’s scope and rollout plan into a structured readiness checklist, launch communications, monitoring plans, rollback procedures, and a post‑launch review agenda. The goal is to reduce surprises and maintain high operational quality.
Steps
Ingest Feature Scope and Rollout Inputs
INGESTCollect the feature scope, rollout strategy, dependencies, and stakeholder list. Normalize these inputs into structured fields for later use.
Confirm Scope and Validate Readiness
EXECUTEAssess technical, product, and support readiness. Identify risks, FAQ gaps, and cross-team alignment needs.
Generate Monitoring and Rollback Plans
EXECUTECreate a monitoring plan with key metrics, alert thresholds, and ownership. Draft a rollback plan that is safe, reversible, and stakeholder-approved.
Prepare Launch Communications
EXECUTEDraft internal and external launch comms using an operational and confident tone. Include support/FAQ notes while ensuring messaging is public-safe and avoids overpromising.
Review and Validate Launch Package
EXECUTEPerform a final validation of the checklist, plans, and communications. Confirm stakeholder approval and readiness to launch.
Create Post-Launch Review Agenda
EXECUTEGenerate a structured agenda for evaluating the launch, including metrics review, incidents, user feedback, and future improvements.
Prompt Configurations
Feature Launch Planning Prompt
You are an operational product launch assistant. Using the provided feature scope, rollout strategy, dependencies, and stakeholder list, produce: (1) a readiness checklist covering tech, product, and support; (2) launch communications written in an operational, confident tone; (3) a monitoring plan with metrics, alert conditions, and owners; (4) a safe and reversible rollback plan; and (5) a structured post-launch review agenda. Include user support/FAQ considerations. Do not overpromise functionality and ensure all content is safe for public distribution. Do not invent facts not provided; if something is missing, reasonably infer industry-standard defaults and clearly mark them as inferred.
Example Inputs/Outputs
Feature scope: real-time dashboard refresh. Rollout: phased rollout to 10% → 50% → 100%. Dependencies: metrics backend, frontend gating. Stakeholders: PM, Eng Lead, Support Lead, Analytics. Generate full launch readiness outputs.
Readiness checklist: engineering sign-off, metrics backend load-test confirmation, support FAQ on refresh frequency, analytics validation of event logging. Launch comms: internal announcement summarizing the phased rollout and user impact; external note emphasizing real-time visibility without overclaiming performance. Monitoring plan: dashboard latency, refresh success rate, API error codes; alerts routed to on-call engineering. Rollback plan: disable feature flag gating the real-time refresh; revert to scheduled refresh mode. Post-launch review agenda: metric stability review, user feedback summary, support ticket trends, lessons learned.