launch

Coordinate product launch readiness and production release execution.

8|Updated May 18, 2026
One-click install
npx skills add https://github.com/lalulali/vespyr --skill launch-lalulali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch
Source: https://github.com/lalulali/vespyr/tree/main/.agents/skills/launch
Command: npx skills add https://github.com/lalulali/vespyr --skill launch-lalulali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates the final stage of product delivery so a completed feature can move safely from development into production. It reduces launch risk by enforcing release readiness checks, stakeholder alignment, rollback planning, and post-launch monitoring.

Core Features & Use Cases

  • Release readiness review: Verifies acceptance criteria, QA, PM sign-off, documentation, security, performance, and observability before launch.
  • Go/no-go orchestration: Structures the launch decision, records risks and mitigations, and blocks release until approvals are aligned.
  • Launch execution and monitoring: Coordinates deployment, feature-flag rollout, health checks, metrics tracking, and early incident response.
  • Post-launch learning: Captures launch retro notes and updates team memory for future releases.
  • Use case: After a feature passes QA, use this Skill to prepare the launch checklist, execute production rollout, monitor adoption and errors, and document lessons learned.

Quick Start

Use the launch skill to review release readiness for the finished feature and prepare the go/no-go launch decision.

Frequently Asked Questions about launch

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

FAQPage Schema
How do I coordinate a product launch and ensure release readiness for completed features?

Coordinate a product launch by enforcing release readiness checks that verify QA, PM sign-off, documentation, and security. This ensures completed features meet all acceptance criteria and stakeholder requirements before moving into production deployment.

What is a go/no-go launch decision and how do I structure stakeholder approval for deployment?

A go/no-go launch decision structures the final release approval by recording risks and mitigations. It blocks production deployment until all required stakeholder approvals are aligned, ensuring coordinated and risk-assessed feature rollout.

How do I plan a rollback and monitor post-launch metrics during feature rollout?

Plan rollback strategies and monitor post-launch metrics by coordinating deployment, feature-flag rollout, and health checks. This tracks adoption rates and errors, enabling early incident response if production deployment issues arise.

Can I use this deployment coordination workflow for software delivery that requires feature-flag rollout?

Yes, this deployment coordination workflow applies to software delivery pipelines requiring feature-flag rollout. It enforces launch checklists, release artifacts, and state-machine updates across planning, operations, and retrospective steps.

What's the best way to document post-launch learning and capture release retrospective notes?

The best way to document post-launch learning is to capture launch retro notes and update team memory during the retrospective phase. This records deployment incidents, monitoring insights, and release lessons for future feature rollouts.

When do I need release management orchestration for production deployment execution?

You need release management orchestration when a completed feature requires stakeholder approval, rollback planning, and post-launch monitoring before production deployment. It enforces observability checks and release artifacts to reduce launch risk.