launch-checklist

Generate multi-department launch checklists with risk tracking and Go/No-Go decisions.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill launch-checklist-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch-checklist
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/launch-checklist
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill launch-checklist-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, phase-driven launch readiness process that ensures every department signs off before release, reducing last-minute surprises and miscommunications.

Core Features & Use Cases

  • Generate a comprehensive multi-department launch checklists covering code, content, store readiness, legal, marketing, and operations.
  • Track risks, blocking items, and conditional items with formal Go/No-Go decision support.
  • Write the finalized checklist to a release file path (e.g., production/releases/launch-checklist-[date].md) and provide a printable summary for stakeholders.

Quick Start

Invoke the skill with /launch-checklist and provide a target launch date or dry-run mode to generate the checklist.

Frequently Asked Questions about launch-checklist

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

FAQPage Schema
How do I create a multi-department launch checklist for release readiness?

Track release risks, blocking items, and conditional items by assessing multi-department validation status and recording formal sign-offs to support structured Go/No-Go decisions for your launch.

What is a Go/No-Go decision process for software launches?

Generate a launch checklist by invoking the skill with a target launch date or dry-run mode, which produces a comprehensive multi-department validation plan and writes the finalized checklist to a release file path.

Do I need sign-offs from all departments before a product launch?

Write the finalized launch checklist to a release file path, such as production/releases/launch-checklist-[date].md, and generate a printable summary to distribute to all relevant stakeholders.

What's the best way to track blocking items and risks during a release?

You can use dry-run mode to generate the checklist without an active release, allowing you to prepare the multi-department validation structure and assess potential risks ahead of the actual launch date.