Launch

Manage software releases with versioning, changelog generation, and rollback planning.

68|14|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/simota/agent-skills --skill launch-simota
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Launch
Source: https://github.com/simota/agent-skills/tree/main/launch
Command: npx skills add https://github.com/simota/agent-skills --skill launch-simota

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured and methodical approach to planning, executing, and tracking software releases, ensuring safety, predictability, and reversibility.

Core Features & Use Cases

  • Release Planning: Define versioning strategies, plan staged rollouts (canary, blue-green), and design rollback procedures.
  • Automated Artifact Generation: Generate CHANGELOG entries and draft release notes from commit history.
  • Use Case: When preparing to deploy a new version of a critical SaaS application, use this Skill to define the release version, generate the user-facing release notes, plan a phased rollout to 10% of users, and confirm a rollback plan is in place before proceeding.

Quick Start

Use the Launch skill to plan the next minor release, including generating a CHANGELOG and defining a rollback strategy.

Frequently Asked Questions about Launch

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

FAQPage Schema
How do I plan a staged rollout for a software release?

To plan a staged rollout, you define the versioning strategy and configure phased deployment patterns like canary or blue-green deployments to ensure release predictability and safety.

How do I generate a changelog and draft release notes from commit history?

Generating a changelog and drafting release notes is handled by automated artifact generation, which parses commit history to produce user-facing release documentation for the new version.

What is the best way to design a rollback procedure for a critical application deployment?

Designing a rollback procedure involves defining explicit recovery steps and guardrails against release anti-patterns before proceeding, ensuring reversibility for critical application deployments.

How does enforcing release criteria prevent common release anti-patterns?

Enforcing release criteria prevents anti-patterns by providing structured guardrails throughout the end-to-end release process, ensuring all deployment safety and predictability requirements are met before execution.

Can I use feature flags for phased rollouts to a subset of users?

Feature flags support phased rollouts by allowing you to route traffic to a subset of users, such as a 10% canary deployment, while maintaining a defined rollback plan if issues arise.