Release Readiness Skill
Use this skill after implementation and focused reviews are substantially
complete, when the remaining question is whether the change is safe to merge or
release. Load the relevant review skill when security, performance,
accessibility, data, or architecture evidence is incomplete.
Apply
review-verification-protocol to
every blocker, risk finding, and ship-or-hold rationale.
Do not use it to replace implementation, a first code review, or a repository's
deployment runbook. Use
semantic-versioning to classify the release
delta and choose or apply a patch, minor, major, or prerelease version;
use
ci-release-engineering to create or
change checked-in CI and release automation, and
container-engineering for Docker/OCI or
Compose implementation.
Workflow
- Confirm scope, acceptance criteria, dependency changes, and the exact release
unit under review.
- Verify test, build, documentation, configuration, migration, compatibility,
and release-note evidence.
- Check rollout, rollback, data recovery, observability, support, and operator
readiness.
- Confirm that security, performance, accessibility, architecture, and domain
risks have either been reviewed or explicitly accepted by the right owner.
- Record skipped checks, assumptions, blockers, follow-ups, and residual risk.
Decide: Ship, Ship With Follow-ups, Hold for Fixes, or Do Not Ship.
Output
Return the decision, evidence, blockers, follow-ups, rollback considerations,
skipped validation, residual risk, and a final release checklist.
1---2name: release-readiness3description: Assess merge and release readiness across tests, docs, migrations, rollout, rollback, operations, and cross-functional risk. Use for a final ship or hold decision; do not use to choose a semantic patch, minor, or major version, or as the primary implementation, code-review, or deployment workflow.4---56# Release Readiness Skill78Use this skill after implementation and focused reviews are substantially9complete, when the remaining question is whether the change is safe to merge or10release. Load the relevant review skill when security, performance,11accessibility, data, or architecture evidence is incomplete.1213Apply14[`review-verification-protocol`](../review-verification-protocol/SKILL.md) to15every blocker, risk finding, and ship-or-hold rationale.1617Do not use it to replace implementation, a first code review, or a repository's18deployment runbook. Use19[`semantic-versioning`](../semantic-versioning/SKILL.md) to classify the release20delta and choose or apply a patch, minor, major, or prerelease version;21use22[`ci-release-engineering`](../ci-release-engineering/SKILL.md) to create or23change checked-in CI and release automation, and24[`container-engineering`](../container-engineering/SKILL.md) for Docker/OCI or25Compose implementation.2627## Workflow28291. Confirm scope, acceptance criteria, dependency changes, and the exact release30 unit under review.312. Verify test, build, documentation, configuration, migration, compatibility,32 and release-note evidence.333. Check rollout, rollback, data recovery, observability, support, and operator34 readiness.354. Confirm that security, performance, accessibility, architecture, and domain36 risks have either been reviewed or explicitly accepted by the right owner.375. Record skipped checks, assumptions, blockers, follow-ups, and residual risk.38 Decide: Ship, Ship With Follow-ups, Hold for Fixes, or Do Not Ship.3940## Output4142Return the decision, evidence, blockers, follow-ups, rollback considerations,43skipped validation, residual risk, and a final release checklist.
nledford