pm-release

To generate a production go-live checklist and rollback plan, you need an interactive tool that parameterizes your release strategy and outputs an action-ready document. This skill produces a written plan covering functional, performance, and security checks after you confirm your release time window and environments.

Coordinating release notifications for a blue-green deployment requires a structured communication workflow. This skill drafts a pre, during, and post-release notification plan alongside your deployment strategy to ensure team alignment throughout the launch process.

Yes, you can create a rollback plan for canary rollouts across multiple environments. The skill supports canary-style release strategies and defines specific rollback triggers and time limits tailored to your selected environments and risk tolerance levels.

A go-live checklist helps with deployment risk control by systematically verifying functional, performance, security, and monitoring requirements before launch. This skill generates this structured checklist to ensure all risk management prerequisites are met before shipping.

Supported release strategies include full, gradual, blue-green, and canary-style deployments. The skill parameterizes the chosen strategy to match your specific risk tolerance and generates a corresponding launch checklist and rollback conditions.

Yes, you need to complete risk management before planning a gradual release. This skill takes completed risk-control outcomes and turns them into a concrete, checklisted release plan so your team can ship with confidence and recover quickly if issues arise.