How do I install the Pmstack Launch Readiness skill?

Run npx skillmds@latest add ryanalberts/pmstack-launch-readiness in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pmstack Launch Readiness safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pmstack Launch Readiness?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pmstack Launch Readiness free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pmstack Launch Readiness?

RyanAlberts (@ryanalberts) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pmstack Launch Readiness by ryanalberts

Name: Pmstack Launch Readiness
Author: RyanAlberts

Pmstack Launch Readiness

Pre-launch verifier. Aggregates PRD, metrics, eval design, eval run, premortem, eval-drift, and brief evidence into a single GO/NO-GO/CONDITIONAL verdict with each item showing pass/fail/missing plus the file that proves it. Trigger when the user says "are we ready to ship," "launch readiness," "release check," "pre-launch review," "ship it?" or asks to gate a release. Run before any launch.

RyanAlberts 74d6e6b 2.6 KB Updated Sep 17, 2026

File contents

launch-readiness — pre-launch evidence gate

A verifier that reads the artifact graph for a feature and returns GO / NO-GO / CONDITIONAL.

Required structure

# launch-readiness — <feature> — <YYYY-MM-DD>
VERDICT: GO|NO-GO|CONDITIONAL

## Checklist
| Item | Status | Evidence |
|---|---|---|
| PRD signed off | Pass/Fail/Missing | <path or "—"> |
| Metrics defined | Pass/Fail/Missing | <path or "—"> |
| Eval designed | Pass/Fail/Missing | <path or "—"> |
| Eval actually run | Pass/Fail/Missing | <path or "—"> |
| No P0 regression (latest eval-drift) | Pass/Fail/Missing | <path or "—"> |
| Premortem completed | Pass/Fail/Missing | <path or "—"> |
| Brief sent | Pass/Fail/Missing | <path or "—"> |

## Verdict reasoning
<2–3 sentences naming the failures or gaps>

Verdict rules

GO — all 7 items Pass.
NO-GO — any P0 item is Fail (PRD missing, eval-drift RELEASE_BLOCKED).
CONDITIONAL — any non-P0 items are Missing or Fail.

Hard rules

Verifier, not generator. Never auto-runs a missing skill to make the verdict GO. Suggest the next command in the verdict reasoning.
NO-GO is honest, not punitive. First-launch with empty outputs/ correctly returns NO-GO.
Acknowledged-gap override. If the PM says "ship anyway" after a NO-GO/CONDITIONAL, append:
```
## Acknowledged gaps
<YYYY-MM-DD> — Shipping despite: <list>
Reason given: <PM-supplied; required, non-empty>
```
And add an additional decision-log line: - <date> — launch-readiness(<feature>): SHIPPED-DESPITE-<gaps> — <path>.
Status values are exactly Pass / Fail / Missing. Three states only.

Where to write

With filesystem: outputs/launch-readiness-<feature>-<YYYY-MM-DD>.md.
Inline (web/mobile): emit the artifact as markdown with the suggested filename at the top.

Decision-log entry

Always: - <date> — launch-readiness(<feature>): <VERDICT> — <path>. On override, an additional SHIPPED-DESPITE-... line.

Tone

Honest, three-state, not punitive. The verdict is information, not a judgment.

Cold-start behavior

Empty outputs/ correctly returns NO-GO with all items Missing. That's the routine working as designed.

---name: pmstack-launch-readinessdescription: Pre-launch verifier. Aggregates PRD, metrics, eval design, eval run, premortem, eval-drift, and brief evidence into a single GO/NO-GO/CONDITIONAL verdict with each item showing pass/fail/missing plus the file that proves it. Trigger when the user says "are we ready to ship," "launch readiness," "release check," "pre-launch review," "ship it?" or asks to gate a release. Run before any launch.---# launch-readiness — pre-launch evidence gateA verifier that reads the artifact graph for a feature and returns **GO / NO-GO / CONDITIONAL**.## Required structure```# launch-readiness — <feature> — <YYYY-MM-DD>VERDICT: GO|NO-GO|CONDITIONAL## Checklist| Item | Status | Evidence ||---|---|---|| PRD signed off | Pass/Fail/Missing | <path or "—"> || Metrics defined | Pass/Fail/Missing | <path or "—"> || Eval designed | Pass/Fail/Missing | <path or "—"> || Eval actually run | Pass/Fail/Missing | <path or "—"> || No P0 regression (latest eval-drift) | Pass/Fail/Missing | <path or "—"> || Premortem completed | Pass/Fail/Missing | <path or "—"> || Brief sent | Pass/Fail/Missing | <path or "—"> |## Verdict reasoning<2–3 sentences naming the failures or gaps>```## Verdict rules- **GO** — all 7 items Pass.- **NO-GO** — any P0 item is Fail (PRD missing, eval-drift RELEASE_BLOCKED).- **CONDITIONAL** — any non-P0 items are Missing or Fail.## Hard rules- **Verifier, not generator.** Never auto-runs a missing skill to make the verdict GO. Suggest the next command in the verdict reasoning.- **NO-GO is honest, not punitive.** First-launch with empty `outputs/` correctly returns NO-GO.- **Acknowledged-gap override.** If the PM says "ship anyway" after a NO-GO/CONDITIONAL, append: ``` ## Acknowledged gaps <YYYY-MM-DD> — Shipping despite: <list> Reason given: <PM-supplied; required, non-empty> ``` And add an additional decision-log line: `- <date> — launch-readiness(<feature>): SHIPPED-DESPITE-<gaps> — <path>`.- **Status values are exactly Pass / Fail / Missing.** Three states only.## Where to write- With filesystem: `outputs/launch-readiness-<feature>-<YYYY-MM-DD>.md`.- Inline (web/mobile): emit the artifact as markdown with the suggested filename at the top.## Decision-log entryAlways: `- <date> — launch-readiness(<feature>): <VERDICT> — <path>`. On override, an additional `SHIPPED-DESPITE-...` line.## ToneHonest, three-state, not punitive. The verdict is information, not a judgment.## Cold-start behaviorEmpty `outputs/` correctly returns NO-GO with all items Missing. That's the routine working as designed.

Frequently asked questions