skills.rest
scomofo
scomofoCOMMUNITY
Explore all skills by this author →
GitHub

launch-checklist

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

Updated Mar 28, 2026
Search Tags:#code quality#checklist#go/no-go#launch readiness#release ops#QA governance
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill launch-checklist-scomofo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: launch-checklist
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/launch-checklist
Command: npx skills add https://github.com/scomofo/dragon-forge --skill launch-checklist-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents costly launch delays and quality issues by systematically validating readiness across code health, content, QA, store assets, legal, and operational readiness.

Core Features & Use Cases

  • Department-by-department readiness checklist: Produces a structured go/no-go checklist covering code, content, QA, store/distribution, legal, infrastructure, community/marketing, and launch operations.
  • Codebase health scanning: Checks for TODO/FIXME/HACK counts, leftover debug output (e.g., console.log/print), placeholder assets, and hardcoded dev/test values.
  • Release artifact creation with a dry-run option: Supports dry-run generation (no file writes/sign-off entries) or interactive saving into production release notes.

Quick Start

Run /launch-checklist with a dry-run argument to generate the full readiness checklist without writing 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 launch readiness checklist for a Godot game release?▼

A go/no-go launch checklist validates game release readiness by auditing codebase health, QA, store distribution, legal, and operations. It systematically prevents costly launch delays by ensuring cross-departmental sign-off before shipping.

What does codebase health scanning check for before a production release?▼

Codebase health scanning checks for TODO, FIXME, and HACK counts, leftover debug output like print statements, placeholder assets, and hardcoded dev/test values. This prevents unresolved code issues from reaching the final release.

Can I perform a dry-run launch audit without writing sign-off entries or files?▼

Yes, you can perform a dry-run launch audit by passing a dry-run argument during invocation. This generates the complete readiness checklist without writing sign-off entries or saving files to production release notes.

What departments are covered in a game release go/no-go readiness validation?▼

A go/no-go readiness validation covers code, content, QA, store distribution, legal, infrastructure, community marketing, and launch operations. This cross-department coverage ensures an auditable release document for production projects.

Does the launch checklist support writing structured output to production release notes?▼

Yes, the launch checklist supports structured output and optional file writing to production release notes. This allows teams to save the final auditable go/no-go decision directly into their release documentation.

Related Skills

Explore More Product & Management Skills→
XGanQAQXGanQAQ
1

release-checklist

Generate a pre-release validation checklist for game releases across platforms.

Community
Advanced
HechaoYannetHechaoYannet

launch-checklist

Generate multi-department launch checklists with risk tracking and Go/No-Go decisions.

Community
Advanced
imgamerimgamer

launch-checklist

Generate a launch readiness checklist with go/no-go sign-offs for game releases.

Community
Advanced
amo-tech-aiamo-tech-ai

production-deploy

Automate production deployment with pre-deploy checks, migrations, and rollback readiness.

Community
Advanced