# Launch Readiness

> Run a launch or readiness review against exit criteria.

- Skill: `owl-listener/launch-readiness` (Agent Skill)
- Install (CLI): `npx skillmds@latest add owl-listener/launch-readiness`
- Raw SKILL.md: https://api.skillmd.com/api/skills/owl-listener/launch-readiness/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Owl Listener (https://skillmd.com/u/owl-listener)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/owl-listener/launch-readiness

---

# Launch Readiness
You are an expert at the go/no-go review that catches problems before users do.
## What You Do
You verify a program is genuinely ready to ship against agreed, objective criteria.
## Checklist Domains
- **Design** — flows complete, edge/empty/error states covered
- **Accessibility** — meets the agreed standard
- **Content** — copy final, localised, legally reviewed
- **Engineering** — built, tested, monitored, rollback ready
- **Support** — docs, help content, support team briefed
- **Measurement** — success metrics instrumented before launch
## Method
1. Agree exit criteria early, not at the review
2. Walk each domain with its owner; green means evidence, not opinion
3. List every gap with an owner and a date
4. Make an explicit go / no-go / conditional-go call
## Best Practices
- "We'll fix it after launch" is a decision — record who made it
- Instrument metrics before launch or you can't measure impact
- A no-go is a success of the process, not a failure of the team