launch-checklist

Generate a department-scoped launch readiness checklist from repository risk markers.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill launch-checklist-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch-checklist
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/launch-checklist
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill launch-checklist-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of costly, last-minute launch failures by providing a structured, cross-department checklist that validates code, content, store, marketing, community, infrastructure, legal, and operations readiness before go-live.

Core Features & Use Cases

  • Launch readiness validation across departments: Covers engineering health, security essentials, content completeness, QA and performance gates, store/distribution assets, legal compliance checks, and operational preparedness.
  • Project-context and release-aware reporting: Pulls relevant context from CLAUDE.md, production milestones, prior release checklists, and an optional live-ops content calendar.
  • Codebase health scanning: Quantifies common release risks (TODO/FIXME/HACK), checks for debug output, placeholder artifacts, and dangerous dev/test configurations.

Example use case: You’re preparing a game or XR app release and need a single source of truth to confirm that the build is stable, assets are final, store pages and legal items are ready, and the team has a day-one monitoring and rollback plan.

Quick Start

Use the launch-checklist skill with the explicit command: /launch-checklist 2026-06-15

Frequently Asked Questions about launch-checklist

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

FAQPage Schema
How do I validate launch readiness across multiple departments before a release?

Launch readiness validation requires a structured checklist covering code, content, store, marketing, infrastructure, legal, and operations. This skill generates department-scoped checklists, scans the codebase for risk markers, and outputs a summary of incomplete departments plus blocking items.

What is a go/no-go release checklist and what does it check?

A go/no-go release checklist is a pre-release validation tool that confirms code stability, content completeness, store assets, and legal compliance. It performs deterministic codebase scanning for TODO/FIXME markers, debug output, and hardcoded dev values to quantify release risks.

How do I scan my codebase for release risk markers like TODO and FIXME?

Codebase scanning for release risk markers involves deterministic checks for TODO, FIXME, and HACK comments, along with debug output, placeholder artifacts, and hardcoded dev values. This skill counts these signals to assess engineering health before go-live.

Can I use a launch checklist for game and XR app releases?

Yes, a launch checklist applies to game and XR app releases by validating build stability, final assets, store pages, and legal items. It pulls project context from milestones and prior release artifacts to confirm operational preparedness and rollback plans.

How do I generate a pre-release checklist that includes infrastructure and legal compliance?

Generating a pre-release checklist for infrastructure and legal compliance requires reviewing project context and prior milestones. This skill produces department-scoped validation items covering security essentials, QA gating, operational preparedness, and legal compliance checks.

What is the best way to track incomplete departments and blocking items before go-live?

Tracking incomplete departments and blocking items before go-live requires a summarized readiness report. This skill outputs a structured summary highlighting conditional and blocking items across all departments to prevent last-minute launch failures.