# Check Launch Readiness

> Reviews launch readiness when asked for a go/no-go assessment or public-launch checklist; separates source checks, provider configuration, and live user journeys.

- Skill: `jovanipink/check-launch-readiness` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx get-skill add jovanipink/check-launch-readiness`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovanipink/check-launch-readiness/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: JovaniPink (https://skillmd.com/u/jovanipink)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/jovanipink/check-launch-readiness

---


# Prelaunch Readiness

Audit only the surface being launched. Read [surface checks](references/surface-checks.md) for the applicable web, service, or application checks.

## Workflow

1. Define the release candidate, revision, target environment, owner, audience, and launch surface.
2. Locate the repository's release contract, runbooks, required checks, and provider configuration.
3. Verify functional, data, security, privacy, accessibility, operability, and rollback evidence proportionate to the launch.
4. Check user-visible claims against actual behavior and maturity. Distinguish prototype, tested, deployed, and publicly available states.
5. Verify platform-only facts from the platform through read-only queries when access exists and the request covers it. Mark them `UNVERIFIED` otherwise.
6. Classify every item as `PASS`, `FAIL`, `WAIVED`, or `UNVERIFIED`; include evidence and waiver owner.
7. Issue `READY`, `BLOCKED`, or `CONDITIONALLY READY` with the smallest list of launch blockers.

## Boundaries

- This skill audits readiness; it does not deploy, change DNS, publish stores, send announcements, or waive failures.
- Do not submit production forms, sign-ins, payments, or test transactions, or create accounts or data, without explicit authorization. Mark that journey `UNVERIFIED` instead.
- A successful build does not prove provider configuration or live behavior.
- A merged change does not prove deployment, traffic, data migration, monitoring, or rollback readiness.
- Do not require irrelevant checklist items merely because they appear in a generic template.

## Example

Synthetic example; not an observed client result.

Input: The build is green, but sign-in has not been tested on the hosted site.

Output: Launch readiness is incomplete. The source check passed; hosted sign-in remains a required user-journey gap.

