Decide whether a release is ready, blocked, still monitoring, or needs rollback using pinned evidence, critical gates, data-change controls, and staged verification.
A green pipeline is not a deployment decision. It may point at the wrong artifact. A schema change may strand the previous application version. A rollback line in a runbook may never have been tested. A timed-out deploy can leave half the fleet changed and make an immediate retry worse.
Deployment Readiness turns that uncertainty into a reviewable release record. It pins the artifact, configuration, environment, authority, and change classes. It then evaluates critical gates for tests, security, compatibility, data changes, observability, rollout, rollback, and ownership. Missing or stale evidence stays visible instead of becoming an unchecked box.
Use it before a production release, for a staged canary, or after a partial or ambiguous deployment. The workflow separates application rollback from data rollback, tests mixed-version compatibility, requires sourced stop triggers, and distinguishes command success from target state and verified outcomes. The included canonical JSON contract and read-only checker make release handoffs easier to review. The checker does not contact CI or production systems.
Version 1.0.0 was reviewed on 2026-07-17 and evaluated through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. The candidate scored 100 across three cases, compared with 74.58 for the same agent without the skill and 74.58 for the exact free upstream. All cases passed. The candidate led the upstream by 11.25 points on a destructive payments migration, 45 points on a canonical canary record, and 20 points on partial-rollout recovery. The evaluation covers those supplied cases. It does not prove a real release is safe, that production evidence is accurate, or that a rollback will work.
The reviewed package SHA-256 is 95ce79578d65c56484f4dc43ec656636359e49e3f572381f2348d6c9a518e532. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
The exact build is green, but the migration drops a column old code still reads. Production scale, lock behavior, restore evidence, mixed-version tests, and deploy approval are missing. The team wants to ship tonight.
Output
A blocked release record with pinned evidence, critical migration and authority gates, an expand-migrate-verify-contract alternative, rollback limits, owners, and one bounded evidence-recovery action.
Input
The artifact, configuration, exact-build checks, baseline, tested rollback, release approval, traffic percentage, observation window, and policy stop triggers are supplied.
Output
A ready-to-deploy canary record with release-bound authority, passed gates, explicit stage entry and exit conditions, untouched post-deploy fields, and no claim that deployment has started.
Provide the target service and environment, release version, commit or artifact digest, configuration and feature-flag revisions, change summary, CI and security results, migration details, current baselines, rollout policy, rollback evidence, owners, approvals, and any prior deploy attempt. Ask for an assessment, plan, recovery decision, verification, or canonical JSON handoff. The skill keeps critical unknowns visible and names one permitted next action.
Service, environment, version, commit or artifact digest, configuration revision, feature-flag state, and intended deployment window.
Exact-build CI and test results, known defects, security findings, dependency and compatibility checks, migration evidence, and stable source locators with timestamps.
Current metric baselines, alert ownership, staged rollout rules, sourced stop triggers, rollback or roll-forward mechanism, and post-deploy checks.
Named release, data, security, and operational owners plus current approval or waiver evidence for the exact release when a deploy decision is requested.
SKILL.md; evidence and critical-gate workflow; data-change, rollout, rollback, and recovery controls; canonical release-record contract; read-only release-record checker; Agent Skills interface metadata
No reviews yet.
Input
The last output says 3 of 10 targets updated. Current target versions, traffic, flags, health, and metrics are unknown, and no rollback decision is authorized.
Output
A blocked recovery record that preserves the attempt, freezes blind retries, reconciles live state by target, and branches among hold, continue, roll forward, rollback, or escalation based on evidence and authority.
Creator
Mmosvio
