skills.rest
WindXRan
WindXRanCOMMUNITY
Explore all skills by this author →
GitHub

launch-checklist

Generates a go/no-go launch readiness checklist across engineering, content, store, legal, and operations for game releases.

Updated Apr 4, 2026
Search Tags:#launch checklist#release readiness#codebase scanning#go no-go#live ops#QA and compliance
One-click install
npx skills add https://github.com/WindXRan/y3td --skill launch-checklist-windxran
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: launch-checklist
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/launch-checklist
Command: npx skills add https://github.com/WindXRan/y3td --skill launch-checklist-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The launch-checklist skill prevents last-minute release failures by turning messy cross-department readiness checks into a structured, auditable go/no-go checklist that can be produced in dry-run or documented for release execution.

Core Features & Use Cases

  • Cross-department readiness validation: Consolidates code, content, QA, store, legal, infrastructure, community, marketing, and operations into one launch plan.
  • Codebase health scanning: Counts TODO/FIXME/HACK markers, flags leftover debug output, and detects placeholder artifacts and dev-only hardcoded values.
  • Release artifact output: Produces a checklist summary and can write it to production/releases/ for the requested launch date.

Quick Start

Run /launch-checklist with argument dry-run to generate a full launch checklist without writing any sign-off entries or files.

Frequently Asked Questions about launch-checklist

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

FAQPage Schema
How do I generate a go/no-go launch checklist for a game release?▼

To generate a go/no-go launch checklist, you can run a dry-run assessment that validates engineering, content, store, legal, and operations readiness. This process scans production milestones and codebase health markers to reduce missed blockers and release risk.

What is codebase health scanning for release readiness?▼

Codebase health scanning for release readiness detects TODO/FIXME/HACK markers, flags leftover debug output, and identifies placeholder artifacts and dev-only hardcoded values. This validates codebase health markers to ensure production stability before a launch.

How do I validate cross-department readiness for a live ops launch?▼

Validating cross-department readiness for a live ops launch consolidates code, content, QA, store, legal, infrastructure, community, marketing, and operations into one structured launch plan. This creates an auditable sign-off checklist to prevent last-minute release failures.

Can I perform a launch readiness dry run without writing release files?▼

Yes, you can execute a dry-run argument to generate a full launch checklist without writing any sign-off entries or files. This allows teams to safely simulate a targeted launch date assessment and identify blockers before actual release execution.

How are launch checklist artifacts documented for production releases?▼

Launch checklist artifacts are documented by optionally writing a dated checklist file directly to production/releases/. This output captures the validated cross-department sign-off summary for the requested launch date, creating an auditable release record.

Related Skills

Explore More Product & Management Skills→
jtvarisjtvaris

release-checklist

Generate a platform-aware release validation checklist from CLAUDE.md and production milestones.

Community
Intermediate
emcconnellemcconnell

launch-checklist

Generate a markdown launch readiness checklist from repository scans and TODO counts.

Community
Advanced
Euraika-LabsEuraika-Labs
14

launch-checklist

Scan game repositories and compile a markdown launch readiness checklist.

Official
Advanced
scomofoscomofo

launch-checklist

Generate a cross-department launch readiness checklist for Godot game releases.

Community
Intermediate