# Ship Readiness

> Check install-to-first-finding metrics, funnel stage, findings state, proofs, and approvals before calling a session ready to ship.

- Skill: `aryaminus/ship-readiness` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add aryaminus/ship-readiness`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aryaminus/ship-readiness/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: Apache-2.0
- Author: aryaminus (https://skillmd.com/u/aryaminus)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/aryaminus/ship-readiness

---


# Ship Readiness Skill

Use this skill when the operator asks whether a mission or session is ready for release.

## Workflow

1. Check session metrics and current funnel stage.
2. Verify there are no unresolved blockers.
3. Confirm proof state and rollback guidance.
4. Summarize approvals, rejections, and any remaining human work.
5. Provide automatic deployment resources via `ck_deployment_advisor` (Dockerize, CI pipes) for the relevant stack (Phoenix, etc.).

## Observability readiness

Before calling a feature ready, check whether relevant local observability evidence exists. Use `ck_observability` reports for `benchmark_history` and `promotions` to summarize readiness, uncovered scenarios, missed runs, and advisory promotion candidates. A ready advisory candidate is not a policy/router/prompt promotion; it still requires explicit human review.

## Additional resources

- [Release checklist](references/release-checklist.md)


Before calling a session ready to ship, inspect `ck_observability` with `report: "loop_status"` when available. Treat it as read-only evidence: unresolved blockers, uncovered observability benchmarks, or non-ready promotion candidates mean the operator should keep the release human-gated.