release-readiness
WAY 12 — go / no-go report for a release or milestone. Use when the user says "release check", "go no go", "are we ready to release", "release readiness" with a milestone or version.
- License 许可
- MIT
- 最近更新
- 2026-11-06
- Stars
- ★ 5
- Forks
- 4
01 前言 Front Matter
- name
- release-readiness
- description
- WAY 12 — go / no-go report for a release or milestone. Use when the user says "release check", "go no go", "are we ready to release", "release readiness" with a milestone or version.
03 SKILL.md 正文
WAY 12 — Release Readiness
Step 1: Gather inputs
- Milestone (required): a milestone title, Jira fixVersion, or Azure iteration path. Ask, and offer the open milestones from recent issues if the user doesn't know it
- Optional thresholds:
--min-pass <pct>(default 95, quarantined tests excluded) ·--allow-sev3 <n>(default unlimited) ·--branch(default: the default branch)
Phase 1: Collect evidence (read-only)
| Signal | Source |
|---|---|
| Open bugs by severity | issue.list (milestone, label bug, open), grouped by sev-* |
Bugs fix-failed / not yet verified |
same list, by label |
| Stories with unanswered Missing Information | issue.list (milestone, label user-story) (plus any with an ACs table). Check each body's Missing Information section |
| Latest QA results | newest qa-artifacts/runs/*/results.json for each test folder whose index **Source:** is in the milestone. Fall back to the newest session report |
| Untested stories | milestone stories with no test folder whose **Source:** points at them |
| CI | ci.latest_run on the branch. Its status, plus the qa-* jobs if ci-test-setup was done |
| Flaky / quarantined | flaky-triage output if run in the last 7 days, otherwise count @quarantine tags |
If a source can't be read, write "unknown" and say why. Never treat unknown as passing.
Phase 2: Verdict
- NO-GO if any of: an open
sev-1orsev-2bug · anyfix-failed· the latest CI run on the branch failed · the QA pass rate is below--min-pass - GO WITH RISKS if no NO-GO condition applies but any of: an open
sev-3above--allow-sev3· untested stories · stories with open Missing Information · quarantined tests in milestone features · an "unknown" signal - GO otherwise
Phase 3: Report
Save ./qa-artifacts/releases/<milestone>-<YYYY-MM-DD>.md:
# Release Readiness — <milestone>
**Verdict: 🔴 NO-GO | 🟠 GO WITH RISKS | 🟢 GO** — <one-line reason>
**Date:** <ISO> · **Branch:** <branch> @ <sha-short>
## Blockers
- <ref> <title> (sev-1) …
## Risks
- …
## Evidence
| Signal | Value | Source |
|---|---|---|
| Open bugs | sev-1: 0 · sev-2: 1 · sev-3: 4 · sev-4: 2 | tracker milestone |
| QA pass rate | 47/50 (94%), 2 quarantined excluded | runs/2026-10-09T14-30-00 |
| CI | ✅ run #8812 on main | code host |
| Untested stories | #151, #155 | traceability |
---
🤖 _Generated by DevOps QA Agent — review before acting on this._
Print the verdict and blockers. Ask the user before filing it as an issue labeled release-readiness. This WAY gives a recommendation. The release decision stays with the team.
04 同仓库更多 Skills
write-tests
WAY 4 — write test cases only, no execution. Use when the user says "write it", "write tests", "generate test cases" — an approved test plan (`Plan:`), or requirements (text or a tracker issue) planned and approved first, optional App/Spec/MR or PR → exactly the planned test files.
verify-fix
WAY 9 — verify that a bug is fixed by running its regression test. Use when the user says "verify it", "verify fix", "is #142 fixed", "check the fix" with one or more bug refs (#142, SHOP-142), or "verify all" for every open bug that has a regression test.
user-story-format
Reference only — the single definition of this project's user-story body (story, Gherkin ACs, Missing Information, DoD) and its AC/scenario rules. Read by user-story-enhancer (WAY 6) and benchmark-gap-story-writer (WAY 8) so stories they write stay identical in shape and WAY 6 can re-score WAY 8's output. Not a workflow on its own.
tracker
Provider-neutral contract for every issue-tracker and code-host action (create/update/comment/close issues, attach files, comment on MRs/PRs, read CI runs and logs) plus label conventions and failure handling. Every WAY calls these operations; the matching provider-* skill says how to perform them on GitLab, GitHub, Jira, Azure DevOps, or Bitbucket.
traceability
WAY 14 — requirements traceability matrix for a user story (each acceptance criterion) or a test folder written from plain text (each R-NN requirement) → the tests covering it → their latest result → open bugs. Use when the user says "trace it", "traceability", "is #148 covered", "coverage of SHOP-148", "trace it <folder>".
test-plan
WAY 19 — design a test plan before any test code. Use when the user says "plan it", "plan tests", "test plan", "design tests" with requirements (text or a tracker issue), optional App/Spec/MR or PR. Output is the test plan (scope, levels, one row per Test#<nn> with category, tags, covers, priority, coverage, entry/exit criteria, risks), reviewed by `review-plan` (WAY 20), filed for approval; `write it Plan:` / `e2e it Plan:` then write exactly that plan. Also holds the plan format every other WAY reads.