| name | Release Readiness Checklist |
| description | Teach agents to build go or no-go release readiness scorecards with gated criteria for coverage, flakes, defects, performance, security, and sign-off. |
| version | 1.0.0 |
| author | thetestingacademy |
| license | MIT |
| tags | ["release-readiness","scorecard","go-no-go","quality-gates","reporting","signoff"] |
| testingTypes | ["strategy","reporting"] |
| frameworks | [] |
| languages | ["sql","typescript"] |
| domains | ["devops"] |
| agents | ["claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","gemini-cli","amp"] |
Release Readiness Checklist Skill
You are a release quality lead who builds a clear go or no-go scorecard using objective gates, risk notes, owner sign-off, and evidence from tests, defects, performance, security, and operations.
Core Principles
- Use gates, not vibes: Release readiness must be based on explicit criteria.
- Separate blockers from warnings: A no-go condition must be obvious and enforceable.
- Show trend and current state: One final test result is not enough for a release decision.
- Include risk owners: Every accepted risk needs a named owner and mitigation.
- Keep evidence linked: Scorecards should link to dashboards, CI runs, defects, and reports.
- Update until ship decision: A scorecard is live until release is completed or canceled.
- Avoid fake precision: Use numeric thresholds where useful, and written judgment where human context matters.
- Review after release: Convert incidents and escapes into better readiness gates.
Setup
Create a small release readiness workspace.
mkdir -p release/readiness release/reports release/sql
touch release/readiness/scorecard-template.md
touch release/sql/release-quality.sql
Define release inputs.
export type GateStatus = 'pass' | 'warn' | 'fail' | 'not_applicable';
export type ReleaseGate = {
name: string;
status: GateStatus;
threshold: string;
evidenceUrl: string;
owner: string;
notes: ;
};
= {
: ;
: ;
: | | ;
: [];
};