What do I need to use Launch Readiness?

Launch name and target date; Launch tier; Completed checklist items or self-assessment; Team and role names.

Is Launch Readiness free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Launch Readiness

Q: How do I know the Launch Readiness output is good?

The skill verifies itself against its own quality checks: Every blocker has a specific owner (not "the team") and a deadline; Rollback plan is explicitly tested, not just written; Analytics events are verified in staging, not just implemented; Go/No-Go decision has a named decision-maker and a cut-off time.

🔵 Stable🕐 updated 2026-06-08 🔷 SkillSpec L3 pm-delivery

Assesses pre-launch readiness across every function and produces an explicit Go / Conditional Go / No-Go recommendation. Use when preparing for any product or feature launch, running a pre-launch review, or determining whether a release is safe to ship. Produces a function-by-function readiness status, a ranked blockers list with owners and deadlines, a risk register, and a clearly reasoned launch recommendation.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸Launch name and target date

▸Launch tier — Tier 1 = major launch / Tier 2 = significant feature / Tier 3 = incremental update

▸Completed checklist items or self-assessment — even partial is fine — we'll surface gaps

▸Team and role names — to assign owners to blockers

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every blocker has a specific owner (not "the team") and a deadline

✓Rollback plan is explicitly tested, not just written

✓Analytics events are verified in staging, not just implemented

✓Go/No-Go decision has a named decision-maker and a cut-off time

✓At least one post-launch monitoring check is scheduled (e.g., T+2hr, T+24hr)

⚠️ What it refuses to do

Do not mark a function as "Ready" without evidence — green status must be backed by a completed checklist item, not an assumption

Do not issue a Conditional Go without specifying exactly what conditions must be met and by when — vague conditions are not conditions

Do not treat the rollback plan as complete unless it has been tested in staging, not just documented

Do not assign blockers to "the team" — every blocker must have a single named owner or it will not be resolved before launch

Do not skip the analytics verification step — unverified tracking events mean the launch will be invisible and cannot be evaluated

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Start with

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="launch-readiness"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Launch Readiness is one of 1078 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog