release-checklist

Generate a pre-release validation checklist from milestone files and TODO counts.

Updated May 13, 2026
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill release-checklist-francisvarga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-checklist
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/release-checklist
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill release-checklist-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents last-minute launch failures by turning a chaotic pre-release rush into a structured, auditable validation checklist aligned to your project milestone.

Core Features & Use Cases

  • Argument-driven platform targeting: Generate PC, console, mobile, or all-platform readiness items using the provided platform argument.
  • Repository health scanning: Quantifies and locates TODO, FIXME, and HACK markers so blockers are surfaced early, alongside whatever test/CI evidence is available.
  • Release artifacts and go/no-go gating: Produces a comprehensive build verification, certification/store metadata, analytics/crash reporting readiness, and sign-off section, and can write the checklist to production/releases/.

Quick Start

Run /release-checklist with the argument platform you’re shipping for (pc, console, mobile, or all) to generate and review the full pre-release checklist.

Frequently Asked Questions about release-checklist

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

FAQPage Schema
How do I generate a pre-release validation checklist for a multi-platform game launch?

To generate a pre-release validation checklist, run the command targeting pc, console, mobile, or all platforms. The Skill reads milestone files and CLAUDE.md, counts TODO/FIXME/HACK markers, and outputs store metadata, platform readiness, and go/no-go sign-off sections.

What is build verification and code hygiene scanning for release readiness?

Build verification and code hygiene scanning quantifies TODO, FIXME, and HACK markers in your repository to surface blockers early. This repository health scanning is combined with milestone review to produce an auditable pre-launch validation checklist.

Can I create a launch readiness checklist for console and mobile store metadata simultaneously?

Yes, you can target console and mobile simultaneously by passing the all-platform argument. The checklist generation produces platform-scoped readiness items alongside store metadata and certification requirements specific to each target.

How do I track milestone progress and identify launch blockers before a release?

Milestone tracking identifies launch blockers by reading current milestone files and scanning the repository for TODO, FIXME, and HACK markers. This data populates a structured checklist with an explicit go/no-go gating section and sign-off list.

Does the release checklist support writing the validation output to a specific project directory?

Yes, the generated checklist can be written directly to the production/releases/ directory. This ensures the release artifacts, build verification results, and QA sign-off lists are stored alongside your project files for auditable tracking.

What is the best way to automate go/no-go gating and QA sign-off for a software release?

Automated go/no-go gating uses repository health scanning and milestone file analysis to produce an explicit sign-off list. This deterministic checklist generation reduces launch risk by validating build verification, store metadata, and platform readiness before approval.