Release Readiness Checklist
Teach agents to build go or no-go release readiness scorecards with gated criteria for coverage, flakes, defects, performance, security, and sign-off.
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- Release Readiness Checklist
- tags
- [ "release-readiness", "scorecard", "go-no-go", "quality-gates", "reporting", "signoff" ]
- agents
- [ "claude-code", "cursor", "github-copilot", "windsurf", "codex", "aider", "continue", "cline", "zed", "bolt", "gemini-cli", "amp" ]
- author
- thetestingacademy
- domains
- [ "devops" ]
- license
- MIT
- version
- 1.0.0
- languages
- [ "sql", "typescript" ]
- frameworks
- []
- description
- Teach agents to build go or no-go release readiness scorecards with gated criteria for coverage, flakes, defects, performance, security, and sign-off.
- testingTypes
- [ "strategy", "reporting" ]
03 SKILL.md 正文
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.
// release/readiness/types.ts
export type GateStatus = 'pass' | 'warn' | 'fail' | 'not_applicable';
export type ReleaseGate = {
name: string;
status: GateStatus;
threshold: string;
evidenceUrl: string;
owner: string;
notes: string;
};
export type ReleaseScorecard = {
releaseName: string;
buildId: string;
decision: 'go' | 'no_go' | 'pending';
gates: ReleaseGate[];
};
Scorecard Template
Use this scorecard for every candidate.
# Release Readiness Scorecard
Release:
Build:
Date:
Decision: Pending
Release owner:
QA owner:
Engineering owner:
## Gates
| Gate | Status | Threshold | Evidence | Owner | Notes |
|---|---|---|---|---|---|
| Unit and integration tests | Pending | 100 percent pass | CI | QA | |
| E2E smoke | Pending | 100 percent pass | CI | QA | |
| Open S1 defects | Pending | 0 | Jira | Product | |
| Open S2 defects | Pending | Approved only | Jira | Product | |
| Flake budget | Pending | Under 2 percent | Test dashboard | QA | |
| Performance budget | Pending | No critical regression | Report | Web lead | |
| Security gate | Pending | No high or critical | Scan | Security | |
| Rollback plan | Pending | Verified | Runbook | DevOps | |
Gate Calculation
Automate the score where data is available.
// release/readiness/evaluate.ts
import type { ReleaseGate, ReleaseScorecard } from './types';
function hasFailedGate(gates: ReleaseGate[]): boolean {
return gates.some((gate) => gate.status === 'fail');
}
function hasPendingGate(gates: ReleaseGate[]): boolean {
return gates.some((gate) => gate.status === 'not_applicable' ? false : gate.status === 'warn');
}
export function evaluateRelease(releaseName: string, buildId: string, gates: ReleaseGate[]): ReleaseScorecard {
const decision = hasFailedGate(gates) ? 'no_go' : hasPendingGate(gates) ? 'pending' : 'go';
return { releaseName, buildId, decision, gates };
}
SQL Evidence Query
Use SQL when release evidence is stored in a warehouse.
select
suite_name,
count(*) as total_tests,
sum(case when status = 'passed' then 1 else 0 end) as passed_tests,
sum(case when status = 'failed' then 1 else 0 end) as failed_tests,
round(100.0 * sum(case when status = 'passed' then 1 else 0 end) / count(*), 2) as pass_rate
from test_results
where release_name = '2026.07'
group by suite_name
order by suite_name;
Go or No-Go Criteria
Use explicit criteria for the meeting.
- No open S1 defects.
- S2 defects have product and engineering approval.
- Critical smoke path passes in the release candidate build.
- Flake rate is below the agreed budget.
- Performance budget has no critical regression.
- Security scan has no high or critical finding.
- Database migrations have rollback or forward-fix plans.
- Monitoring and alerting are active.
- Support and operations know the release window.
- Rollback owner is present or delegated.
Sign-Off Workflow
Record sign-off as a decision log.
## Sign-Off
QA: Approved, smoke and regression gates pass.
Engineering: Approved, rollback plan verified.
Product: Approved, accepted S2 risk QA-4281.
Security: Approved, no high or critical findings.
DevOps: Approved, monitors active and release window staffed.
Decision: Go
Time:
Decision owner:
Reference Table
| Gate | Pass | Warn | Fail |
|---|---|---|---|
| Open S1 defects | 0 | Not used | Any open S1 |
| Open S2 defects | 0 | Accepted risk | Unapproved S2 |
| Smoke tests | 100 percent pass | Retry under review | Any confirmed fail |
| Flake budget | Under 2 percent | 2 to 5 percent | Over 5 percent |
| Performance | Within budget | Small accepted regression | Critical path regression |
| Security | No high or critical | Medium findings tracked | High or critical |
Common Mistakes
- Holding a go or no-go meeting without current evidence.
- Treating all defects as equal.
- Forgetting rollback readiness.
- Allowing accepted risk with no owner.
- Using a scorecard that cannot produce no-go.
- Ignoring flaky tests because the last run passed.
- Leaving performance and security outside release readiness.
- Not recording the final decision.
- Changing thresholds during the meeting.
- Failing to review release escapes afterward.
Checklist
- [ ] The release candidate build is identified.
- [ ] All gates have thresholds.
- [ ] Evidence links are current.
- [ ] S1 and S2 defect status is reviewed.
- [ ] Flake budget is calculated.
- [ ] Performance budget is reviewed.
- [ ] Security findings are reviewed.
- [ ] Rollback plan is verified.
- [ ] Sign-off owners are recorded.
- [ ] Final decision is logged.
04 同仓库更多 Skills
nemoclaw-user-reference
Describes the NemoClaw integration layer and blueprint architecture and how they orchestrate compatible agent sandboxes. Use when looking up architecture, agent integration, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw agent architecture, nemoclaw plugin blueprint structure, nemoclaw vs openshell, which cli, nemoclaw cli, openshell cli, sandbox commands, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.
nemoclaw-user-overview
Explains how OpenClaw, OpenShell, and NemoClaw form the ecosystem, NemoClaw's position in the stack, what NemoClaw adds beyond the community sandbox, and when to prefer NemoClaw versus integrating OpenShell and OpenClaw directly. Use when users ask about the relationship between OpenClaw, OpenShell, and NemoClaw, or when to use NemoClaw versus OpenShell. Trigger keywords - nemoclaw ecosystem, openclaw openshell, nemoclaw vs openshell, sandboxed openclaw, how nemoclaw works, nemoclaw sandbox lifecycle blueprint, nemoclaw overview, openclaw always-on assistants, nvidia openshell, nvidia nemotron, nemoclaw release notes, nemoclaw changelog.
nemoclaw-user-monitor-sandbox
Inspects sandbox health, traces agent behavior, and diagnoses problems. Use when monitoring a running sandbox, debugging agent issues, or checking sandbox logs. Trigger keywords - monitor nemoclaw sandbox, debug nemoclaw agent issues.
nemoclaw-user-manage-sandboxes
Explains operational tasks after the quickstart: listing sandboxes, status and health checks, logs, diagnostics, port forwards, multiple sandboxes, credential reset, rebuilds, network presets, upgrades, and uninstall. Trigger keywords - manage nemoclaw sandboxes, nemoclaw status, nemoclaw list, nemoclaw dashboard port, nemoclaw rebuild, nemoclaw upgrade sandboxes, nemoclaw uninstall, sandbox mutability, sandbox runtime configuration, sandbox rebuild, nemoclaw backup, nemoclaw restore, workspace backup, openshell sandbox download upload, nemoclaw messaging channels, nemoclaw telegram, nemoclaw discord, nemoclaw slack, nemoclaw wechat, nemoclaw whatsapp, openshell channel messaging, nemoclaw workspace files, soul.md, user.md, identity.md, agents.md, sandbox persistence.
nemoclaw-user-manage-policy
Adds, removes, or modifies allowed endpoints in the sandbox policy. Use when customizing network policy, changing egress rules, or configuring sandbox endpoint access. Trigger keywords - customize nemoclaw network policy, sandbox egress policy configuration, nemoclaw integration policy examples, post-install policy setup, openshell approval workflow, policy preset, nemoclaw approve network requests, sandbox egress approval tui.
nemoclaw-user-get-started
Installs NemoClaw, launches a sandbox, and runs the first agent prompt. Use when onboarding, installing, or launching a NemoClaw sandbox for the first time. Trigger keywords - nemoclaw quickstart, install nemoclaw openclaw sandbox, nemohermes quickstart, hermes agent nemoclaw, run hermes openshell sandbox, nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.