Release Readiness
Purpose
Produce an evidence-backed ready, not ready, or ready with accepted risks verdict. Assessment does not authorize release actions.
Workspace protocol
Read references/workspaces.md once per agent task before selecting or creating workflow artifacts; reuse it unless repository scope or task authority changes. This skill owns only the task-specific behavior below.
Inputs
- Release scope, target environment, acceptance criteria, and rollout expectations
- Current worktree or candidate, CI results, tests, findings, migrations, docs, and operational signals
- Rollback, observability, compatibility, and ownership information
Outputs
- Verdict with blockers, accepted risks, and evidence
- Checklist covering code quality, tests, build, security, data change, compatibility, observability, rollback, docs, and support readiness as applicable
- Exact unverified items and required next actions
Rules
- For a selected work item, read its acceptance criteria, current plan state, findings, and verification evidence when available before judging readiness; reading this state neither authorizes release nor by itself requires artifact mutation.
- When findings affect the verdict, read
references/finding-rubric.md and verify their severity and disposition instead of trusting uncalibrated labels.
- Treat
clean_with_residuals as a disclosed qualified completion, not evidence that every reported risk was fixed; include its residual ledger in the readiness verdict.
- Inspect current state; do not rely on stale claims that checks passed.
- Run the strongest safe local checks and distinguish local proof from CI, staging, and production proof.
- Treat code complete, merge ready, deploy ready, deployed, and verified in production as separate states.
- Block on open critical or high findings unless risk is explicitly accepted by the proper owner.
- Do not merge, tag, publish, deploy, or migrate without explicit authorization.
Decision-log updates
Record risk acceptance, waived gates, rollout or rollback choices, and readiness verdict changes with evidence. Link unresolved findings and owners.
When durable state is approved, append only accepted release risk, waivers, rollback choices, and readiness-scope decisions to the selected work item's decisions.md; otherwise include them in the final response.
Escalate to the human
Escalate for blocked gates, missing rollback for high-risk changes, unresolved ownership, destructive migration, compliance or security risk, production action, or any request to waive a required control.
1---2name: release-readiness3description: Use when a change, branch, build, migration, or release candidate must be assessed before merge, deployment, rollout, or handoff.4---56# Release Readiness78## Purpose910Produce an evidence-backed `ready`, `not ready`, or `ready with accepted risks` verdict. Assessment does not authorize release actions.1112## Workspace protocol1314Read `references/workspaces.md` once per agent task before selecting or creating workflow artifacts; reuse it unless repository scope or task authority changes. This skill owns only the task-specific behavior below.1516## Inputs1718- Release scope, target environment, acceptance criteria, and rollout expectations19- Current worktree or candidate, CI results, tests, findings, migrations, docs, and operational signals20- Rollback, observability, compatibility, and ownership information2122## Outputs2324- Verdict with blockers, accepted risks, and evidence25- Checklist covering code quality, tests, build, security, data change, compatibility, observability, rollback, docs, and support readiness as applicable26- Exact unverified items and required next actions2728## Rules2930- For a selected work item, read its acceptance criteria, current plan state, findings, and verification evidence when available before judging readiness; reading this state neither authorizes release nor by itself requires artifact mutation.31- When findings affect the verdict, read `references/finding-rubric.md` and verify their severity and disposition instead of trusting uncalibrated labels.32- Treat `clean_with_residuals` as a disclosed qualified completion, not evidence that every reported risk was fixed; include its residual ledger in the readiness verdict.33- Inspect current state; do not rely on stale claims that checks passed.34- Run the strongest safe local checks and distinguish local proof from CI, staging, and production proof.35- Treat code complete, merge ready, deploy ready, deployed, and verified in production as separate states.36- Block on open critical or high findings unless risk is explicitly accepted by the proper owner.37- Do not merge, tag, publish, deploy, or migrate without explicit authorization.3839## Decision-log updates4041Record risk acceptance, waived gates, rollout or rollback choices, and readiness verdict changes with evidence. Link unresolved findings and owners.42When durable state is approved, append only accepted release risk, waivers, rollback choices, and readiness-scope decisions to the selected work item's decisions.md; otherwise include them in the final response.4344## Escalate to the human4546Escalate for blocked gates, missing rollback for high-risk changes, unresolved ownership, destructive migration, compliance or security risk, production action, or any request to waive a required control.
nono911