release-checklist

Generate a pre-release validation checklist with TODO, FIXME, and HACK scanning.

70|42|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill release-checklist-tranhieutt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-checklist
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/release-checklist
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill release-checklist-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates release readiness into a single guided checklist so build verification, certification tracking, and launch tasks never get overlooked before shipping.

Core Features & Use Cases

  • Holistic release checklist: reads CLAUDE.md, milestone details, and repository comments to count TODO/FIXME/HACK items, review test outputs, and surface known blockers.
  • Platform-specific coverage: adapts sections for PC, console, and mobile requirements, plus store metadata, legal, and launch readiness gates tailored per platform argument.
  • Use Case: the producer running final QA can ask for the checklist, review platform sections, and archive the validated document for sign-off.

Quick Start

Ask the release-checklist skill to produce a readiness checklist for the current milestone covering all platforms before release.

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 my current milestone?

Generate a pre-release validation checklist by reading CLAUDE.md context, analyzing production milestones, counting TODO/FIXME/HACK items, reviewing test outputs, and saving the result to production/releases/release-checklist-[version].md.

What should a release readiness checklist cover for multi-platform game launches?

A release readiness checklist should cover build health, platform certification, metadata, store readiness verification, and known blockers tailored for PC, console, and mobile launches.

Can I adapt launch readiness verification scenarios for different platforms?

Yes, the checklist adapts sections for PC, console, and mobile requirements, generating platform-specific store metadata, legal checks, and launch readiness gates.

How does a QA playbook track build verification and blocker counts before shipping?

A QA playbook tracks build verification by reading milestone details, reviewing test result outputs, noting blocker counts, and consolidating launch tasks into a single validated document for sign-off.