launch-checklist

Generate a markdown launch readiness checklist from repository scans and TODO counts.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/emcconnell/nova-scout --skill launch-checklist-emcconnell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch-checklist
Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/launch-checklist
Command: npx skills add https://github.com/emcconnell/nova-scout --skill launch-checklist-emcconnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates and automates pre-launch validation across engineering, content, store, marketing, community, infrastructure, legal, and sign-off workflows so teams can identify blocking issues and confidently decide go/no-go.

Core Features & Use Cases

  • Repository and milestone scan: Reads CLAUDE.md, the latest milestone, existing release checklists, and content calendars to gather context for the release.
  • Codebase health checks: Counts TODO/FIXME/HACK markers, searches for debug outputs and hardcoded test values, and flags placeholder assets and dev-only flags.
  • Checklist generation and persistence: Produces a detailed Markdown launch checklist with counts, blocking/conditional items, department summaries, and can optionally save the checklist to production/releases when not in dry-run mode.
  • Use Case: A release manager runs the skill before a scheduled launch or a dry-run to produce a prioritized list of fixes, required sign-offs, and an actionable day-one plan.

Quick Start

Run the launch-checklist skill with a target date or 'dry-run' to produce a complete pre-launch checklist and summary.

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 pre-launch readiness checklist for a software release?

Generate a pre-launch readiness checklist by scanning repository files like CLAUDE.md, milestones, and release notes to assess code health, content, and infrastructure. This produces a markdown checklist summarizing blocking items, department gaps, and required sign-offs for confident go/no-go decisions.

How do I scan my codebase for debug artifacts and TODO markers before a launch?

Scan your codebase for debug artifacts and TODO markers by counting TODO, FIXME, and HACK flags, detecting debug outputs, and searching for hardcoded test values. The process flags placeholder assets and dev-only flags to identify blocking issues before release.

What is cross-team launch readiness validation for engineering and marketing teams?

Cross-team launch readiness validation consolidates pre-launch checks across engineering, content, store, marketing, community, infrastructure, legal, and sign-off workflows. It identifies department gaps and blocking issues so teams can confidently decide whether to proceed with a scheduled launch.

Can I run a dry-run launch checklist without writing files to my repository?

Yes, you can run a dry-run launch checklist to review all counts, blocking items, and department gaps without modifying your repository. The checklist only writes to production/releases when explicitly not in dry-run mode, keeping your file system untouched during testing.

Does the launch checklist assess readiness across departments beyond engineering?

Yes, the launch checklist assesses readiness across content, store, marketing, community, infrastructure, and legal departments in addition to engineering. It reads content calendars and milestone data to produce department summaries and identify gaps requiring sign-off.

What are the limitations of automating release sign-off workflows with a checklist?

Automating release sign-off workflows with a checklist is limited to scanning repository files, counting code markers, and detecting debug artifacts. It cannot verify external infrastructure health or enforce legal compliance, serving only as a summary and gap-analysis tool for human go/no-go decisions.