aryaminus Ship Readiness Skill
Use this skill when the operator asks whether a mission or session is ready for release.
Workflow
- Check session metrics and current funnel stage.
- Verify there are no unresolved blockers.
- Confirm proof state and rollback guidance.
- Summarize approvals, rejections, and any remaining human work.
- 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
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.