agentsclimarketplace

Launch readiness

Skill janellecipriano/pm-skills/skills/launch-readiness

Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.

Install
npx -y skills add janellecipriano/pm-skills --skill launch-readiness

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run a go/no-go launch-readiness review for a product or feature release across all functions (product, eng, QA, design, docs, support, marketing, legal, ops). Use when the user says "launch readiness", "go/no-go", "are we ready to ship/launch", "release checklist", or needs a cross-functional sign-off before shipping.

SKILL.md

2.2 KB, as published. Nobody here has run it

Launch Readiness

Drive a cross-functional readiness review that ends in a clear Go / No-Go / Go-with-conditions recommendation.

When to use

  • Approaching a release and you need to confirm every function is ready.
  • Preparing a go/no-go meeting or sign-off doc.

Inputs to gather

  • What's launching, the target date/window, and the rollout plan (e.g., %-based, regions, GA vs. beta).
  • Status by function; known open issues and their severity.
  • Success metrics and the rollback/kill-switch plan.

Process — review each readiness area

For each area, capture status (🟢/🟡/🔴), owner, evidence/notes, and blocking?:

  1. Product/Scope — acceptance criteria met; scope cuts agreed.
  2. Engineering — code complete, feature-flagged, perf/scale checked, on-call ready.
  3. Quality — test pass, critical bugs triaged to zero, edge cases covered.
  4. Design/UX — final review, accessibility, edge/empty/error states.
  5. Docs & Support — help content, runbooks, support team briefed.
  6. Go-to-market — comms, release notes (release-notes), pricing/packaging if relevant.
  7. Legal/Privacy/Compliance — reviews and approvals where required.
  8. Data/Analytics — instrumentation live; success metrics measurable.
  9. Rollout & rollback — staged plan, monitoring/alerts, tested rollback, named decision owner.

Decision

  • Go — all critical areas green.
  • Go with conditions — minor ambers with named owners + dates; list the conditions.
  • No-Go — any red in a blocking area; state what must close and the re-review date.

Output format

A readiness table (area · status · owner · notes · blocking?) followed by the recommendation, the conditions/blockers, and the rollback plan. State the decision owner and the go/no-go meeting time.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.