launch-checklist

Generate prioritized launch checklists with owners, dependencies, and timelines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates fragmented launch planning into a single, prioritized checklist so product teams avoid missed steps, unclear ownership, and last-minute surprises across pre-launch, launch, and post-launch phases.

Core Features & Use Cases

  • Prioritized checklists: Generates P0/P1/P2 items with explicit owners, due dates, and rollout strategy tailored to small features, major launches, or regulatory releases.
  • Dependency & critical-path analysis: Identifies blocked/blocking items, traces the longest dependency chain, computes total duration, and flags launch-at-risk scenarios.
  • Integrations & outputs: Produces a markdown checklist saved to outputs/launches/, offers templates, and can convert items into Jira/Linear tasks or calendar milestones for execution.
  • Use Case: Create a four-week launch plan for a checkout redesign that includes engineering, design, legal, analytics, support, and marketing steps with clear rollback and kill criteria.

Quick Start

Create a launch checklist for the checkout redesign targeting March 15 with owners, priorities, dependencies, critical path, and a saved markdown output.

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 product launch checklist with owners, dependencies, and priorities?

A product launch checklist consolidates fragmented planning into a single prioritized list with P0/P1/P2 items, explicit owners, due dates, and dependency chains to avoid missed steps and last-minute surprises across pre-launch, launch, and post-launch phases.

How does critical path analysis work for go-to-market planning?

Critical path analysis for go-to-market planning traces the longest dependency chain in your launch checklist, computes total duration, identifies blocked and blocking items, and flags launch-at-risk scenarios based on your rollout strategy.

Can I convert a launch planning checklist into Jira or Linear tasks?

Yes, you can convert your launch planning checklist into Jira or Linear tasks because the Skill produces a markdown output with explicit owners, priorities, and due dates suitable for direct ticketing and calendar integration.

Does this launch planning approach work for regulatory products and small features?

This launch planning approach works for regulatory products and small features by tailoring prioritized checklists, rollback criteria, and rollout strategies to scale across minor feature drops and major releases with appropriate dependency tracking.

What is the best way to define kill criteria and rollback strategies in a launch checklist?

The best way to define kill criteria and rollback strategies in a launch checklist is to generate a comprehensive plan that includes engineering, design, legal, and support steps with explicit rollout strategies and clear termination conditions for launch-week execution.