Skip to content

deanpeters/Product-Manager-Skills / plugins/pm-develop/skills/release-readiness

release-readiness

Verified

Check a release is safe to ship: tests, rollout, monitoring, rollback, support. Use when a build is about to go out and you need to know what could hurt, and how you'd undo it.

FileKindSize
SKILL.mdskill md10.8 KB
examples/sample-industrial.mdmarkdown2.2 KB
examples/sample.mdmarkdown2.0 KB
template.mdmarkdown1.4 KB

template.md

View on GitHub
# Release Readiness Template

Unconfirmed items are `[NEEDS SOURCE]` or "not confirmed", never assumed done.

---

## 1. The release
**What is shipping:** · **What does not change:** · **Reaches (accounts / units):** · **Reversibility:**
**Level:** [1 Light / 2 Standard / 3 Heavy] because [reach and reversibility]. A lighter level would leave [uncovered].

## 2. The seven checks
| Check | State | Evidence | Owner |
|---|---|---|---|
| 1. What changes (and doesn't) | | | |
| 2. Tested: what, where, **what was not tested** | | | |
| 3. Rollout stages and move-on criteria | | | |
| 4. Monitoring: signals, watcher, duration | | | |
| 5. Rollback: method, time, rehearsed? | | | |
| 6. Support and customer communication | | | |
| 7. Dependencies and timing (why now) | | | |

## 3. Go / hold criteria (agreed before the status)
| # | Criterion | Threshold | Must-pass or Watch | Result |
|---|---|---|---|---|

## 4. Decision
**Go / Hold / Go with conditions:** · **Decided by (one person):** · **Conditions:**
**Open items:** [owner, date]

---

## Quality checks
- [ ] Level is justified by reach and reversibility
- [ ] Rollback is named, timed, and rehearsed (or its absence is flagged)
- [ ] Rollout is staged with criteria
- [ ] Monitoring has named signals and a named watcher
- [ ] Go/hold criteria were written before the status
- [ ] One person decides
- [ ] Why-now is justified
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 323kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 323kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 323kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall