release-readiness
Decides go or no-go for a release with evidence: exit criteria, test results by risk, open defects, non-functional results, rollback and monitoring readiness. Use when the user says 'go no-go' or asks 'are we ready to release'. Not for planning the testing (use test-planning).
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- release-readiness
- license
- Apache-2.0
- description
- Decides go or no-go for a release with evidence: exit criteria, test results by risk, open defects, non-functional results, rollback and monitoring readiness. Use when the user says 'go no-go' or asks 'are we ready to release'. Not for planning the testing (use test-planning).
- argument-hint
- [release, version or date]
03 SKILL.md 正文
release-readiness
Objective
A release decision needs facts, not a feeling. This skill collects the evidence for one release and compares it with the exit criteria. Then it gives a clear recommendation, with the reasons and the owners: go, go with known risks, or no-go.
Context
- Read
.agents/qa-project-context.mdif it exists. Use its release criteria, critical journeys, environments and pipeline. - If it does not exist, ask the user for the release criteria. Suggest
qa-project-contextonce. - Read the test plan of the release, if one exists.
Discovery questions
- Which version, which changes, and which date?
- What are the exit criteria? Who makes the final decision?
- Where are the test results, the defect list and the monitoring dashboards?
Workflow
- Scope: the changes in the release, and their risk (see
risk-based-testing). - Evidence, for the release candidate build and commit only:
- test results by level, with skipped and quarantined tests listed
- the coverage of the high-risk items (tested, partly tested, not tested)
- open defects by severity, with the decision for each critical and major one
- non-functional results (performance, security, accessibility) where the plan requires them
- contract and compatibility checks for changed interfaces
- data migrations tested on realistic data
- Operational readiness: a rollback or a feature flag for each risky change, monitoring and alerts for the critical journeys, smoke checks after the deploy, on-call owners.
- Compare each exit criterion with the evidence: met, not met, or not measured.
- Recommend: GO, GO WITH RISKS (each risk with an owner and a mitigation), or NO-GO (the blocking items).
Output
## Release readiness: <version>
Recommendation: GO | GO WITH RISKS | NO-GO
| Exit criterion | Evidence | Status |
|---|---|---|
Open risks: <risk> - owner - mitigation
Blocking items: ...
After release: smoke checks, monitors to watch, rollback trigger
Anti-patterns
- Evidence from an older build. It proves nothing about the candidate.
- Skipped or quarantined tests counted as passed.
- "No known bugs" when the high-risk items were not tested.
- No rollback plan for a risky change.
Done when
- Each exit criterion has evidence from the candidate build, or is marked "not measured".
- Each open critical or major defect has a decision.
- The recommendation states the risks with owners, or the blocking items.
- The post-release checks and the rollback trigger are defined.
Related skills
test-planning: the exit criteria.risk-based-testing: the high-risk items.test-runner: the current results.quality-postmortem: learn from what escaped.test-review-panel: a merged review of the release changes.
04 同仓库更多 Skills
unit-testing
Writes, fixes or improves unit tests for rules, calculations, validation and state logic: arrange-act-assert, exact oracles, boundary sets, doubles only at boundaries, controlled clock and randomness. Use when the user says 'write unit tests', 'TDD this' or 'mock this dependency'. Not for HTTP endpoints (use api-testing).
ui-automation
Writes, fixes or structures browser end-to-end tests for critical journeys: role, label or test ID locators, auto-waiting assertions, API data setup, page objects, auth reuse and traces. Use when the user says 'UI test', 'end-to-end test' or 'our UI tests are brittle'. Not for business rules (use unit-testing).
testcase-reviewer
Reviews automated tests or manual test cases like a senior test architect: scores fidelity, oracles, assertion depth, edge cases and determinism, and finds tests that pass on wrong code. Use when the user says 'review my tests', 'test smells' or 'review AI-written tests'. Not for fault injection (use mutation-probe).
testability-review
Scores how testable a feature, module or design is before tests exist (seams for clock, randomness and network, hidden state, observability) and gives the smallest production change per blocker. Use when the user asks 'is this testable' or 'why is this hard to test'. Not for writing the tests (use unit-testing).
test-strategy
Writes a test strategy for a product, system or team: quality goals, test levels and their share, environments, data, automation scope, non-functional testing, metrics and a roadmap. Use when the user says 'test strategy' or 'QA strategy'. Not for one sprint or release plan (use test-planning).
test-runner
Finds how a project runs its tests, runs the right subset, and triages each failure as product bug, test defect, environment problem or flaky test, with evidence. Use when the user says 'run the tests' or asks 'which tests fail and why'. Not for pipeline design (use ci-cd-integration).