launch

Guide software releases through gated audits, deployment confirmation, and post-launch verification.

23|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/tombensim/pi-wizard --skill launch-tombensim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch
Source: https://github.com/tombensim/pi-wizard/tree/main/examples/launch
Command: npx skills add https://github.com/tombensim/pi-wizard --skill launch-tombensim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The launch process can fail in expensive ways when teams skip repeatable checks, overlook security and quality risks, or deploy without a clear confirmation gate.

Core Features & Use Cases

  • Pre-Launch Audit with Hard Guardrails: Runs ordered checks (git cleanliness, branch validation, tests, lint/type-check when detected, security audit, environment validation, and production build) and blocks deployment if tests fail.
  • Summary Confirmation Gate: Forces an explicit user review before deployment proceeds, including product name, version, launch type, and target environment.
  • Deployment + Post-Launch Verification: Executes deployment via detected platform conventions, verifies health/homepage/error signals after release, and recommends adding rollback steps if verification fails.
  • Traceability & Safety for Sensitive Output: Requires git tagging for releases and ensures security audit results are not truncated while providing safer handling for sensitive values.

Quick Start

Run the launch wizard to generate a gated product deployment plan for your repo by starting the demo command /launch.

Frequently Asked Questions about launch

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

FAQPage Schema
How do I block a production deployment if tests fail or the git branch is dirty?

A product launch workflow with hard guardrails blocks deployment on test failures by validating git cleanliness, running ordered checks, and enforcing a summary confirmation gate before proceeding. This prevents deploying unverified code.

What is a deployment gate in a CI/CD pipeline and how does it work?

A deployment gate is an explicit confirmation step that pauses a product launch for user review. It requires accepting a summary of the product name, version, launch type, and target environment before deployment executes.

Can I use a product launch workflow for different tech stacks and frameworks?

Yes, the launch workflow dynamically adapts to common tech stacks by detecting available test, lint, type-check, security audit, build, and deployment mechanisms to orchestrate the gated release process accordingly.

How do I verify application health and plan a rollback after a release?

Post-launch verification checks health, homepage, and error signals after deployment. If verification fails, the workflow recommends adding rollback steps and enforces creating release tags for traceability.

How do I run a security audit before deploying without losing sensitive findings?

The pre-launch audit runs a security check as part of its ordered phases and preserves full findings without truncation, ensuring sensitive values are handled safely while blocking deployment on critical failures.

How do I add conditional steps like marketing prep to a software release process?

A launch wizard orchestrates a gated deployment plan that supports conditional phases like marketing prep, integrating these steps alongside mandatory security audits and post-launch verification.