# Release Readiness Checklist

> Inspect a small npm CLI release candidate and produce a row-by-row release-readiness checklist report with evidence, pass rules, severity, N/A policy, and a final gate. Use when the task is to review a release candidate without publishing it.

- Skill: `learnprompt/release-readiness-checklist` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add learnprompt/release-readiness-checklist`
- Raw SKILL.md: https://api.skillmd.com/api/skills/learnprompt/release-readiness-checklist/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: learnprompt (https://skillmd.com/u/learnprompt)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/learnprompt/release-readiness-checklist

---


# Release readiness checklist

## When to use

Use this skill when the user asks for a release-readiness check, release candidate inspection, pre-publish checklist, or dry-run go/no-go decision for a small npm CLI package.

## Workflow

1. Read `references/checklist-contract.md`.
2. Run:

   ```bash
   node .agents/skills/release-readiness-checklist/scripts/collect-evidence.mjs \
     --expected-version 1.4.0 \
     --output-json reports/release-readiness.json \
     --output-md reports/release-readiness.md
   ```

3. Keep the generated report even if the exit code is non-zero. The point is to preserve evidence, not to stop at the first failing row.
4. Run `npm test`.
5. Return only the JSON object requested by the caller schema.

## Boundaries

- Never run `npm publish`.
- Never edit `package.json`, `CHANGELOG.md`, or `release/install-command.txt`.
- Do not replace checklist rows with “looks fine” prose.
- If the host blocks the skill or model execution, report that block plainly instead of fabricating a pass.