launch-checklist

Generate a Markdown launch readiness checklist from project context and codebase health.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill launch-checklist-jtvaris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch-checklist
Source: https://github.com/jtvaris/sunday-night-dynasty/tree/main/.agents/skills/launch-checklist
Command: npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill launch-checklist-jtvaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complete launch readiness validation across every department, producing a unified sign-off checklist to prevent missed steps from code, content, store, marketing, community, infrastructure, and legal.

Core Features & Use Cases

  • Reads project context from CLAUDE.md, latest production milestones, current release checklists, and the content calendar.
  • Scans codebase health for TODO/FIXME/HACK counts, debug output, placeholder assets, and hardcoded dev/test values.
  • Generates a detailed Markdown launch checklist and saves it to production/releases/launch-checklist-[date].md; supports a dry-run mode.

Quick Start

Provide a launch date or 'dry-run' to generate the full launch readiness checklist.

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 software release?

To generate a launch readiness checklist, provide a launch date or specify dry-run. The system reads project context like CLAUDE.md, latest milestones, and content calendars, then saves a Markdown sign-off checklist to production/releases/launch-checklist-[date].md.

What does a launch readiness validation check for in a codebase?

A launch readiness validation scans codebase health for TODO, FIXME, and HACK counts, debug output, placeholder assets, and hardcoded dev or test values. This ensures code quality before producing the final sign-off checklist.

Can I test launch checklist generation without affecting production files?

Yes, you can run a dry-run to test launch checklist generation. This simulates the comprehensive readiness validation and produces the checklist without saving the final Markdown file to the production directory.

What project context is needed to produce an accurate release sign-off checklist?

Producing a release sign-off checklist requires project context from CLAUDE.md for tech stack and team structure, the latest production milestone, current release checklists, and the content calendar if available.

Why use automated launch readiness validation instead of a manual release checklist?

Automated launch readiness validation orchestrates cross-departmental checks across code, content, store, marketing, community, infrastructure, and legal, preventing missed steps that manual release checklists often overlook.