deanpeters/Product-Manager-Skills / plugins/pm-develop/skills/release-readiness
release-readiness
VerifiedCheck 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.8 KB |
| examples/sample-industrial.md | markdown | 2.2 KB |
| examples/sample.md | markdown | 2.0 KB |
| template.md | markdown | 1.4 KB |
examples/sample.md
View on GitHub# Release Readiness Example: SaaS
**Release:** change to how overage is billed (Fieldlight). Reaches all paying accounts.
**Why this example exists:** a billing change is invisible to users until it's wrong, so it earns
Level 3 even though it's a small code change.
---
```markdown
## The release
**What changes:** overage computed per technician-day instead of per month.
**What does not change:** base plan prices, invoice layout.
**Reaches:** all ~1,400 paying accounts. **Reversibility:** a feature flag undoes the calculation,
but invoices already issued would need credit notes.
**Level:** 3 Heavy. Reach is total and a wrong invoice is hard to undo.
## The seven checks
| Check | State | Evidence |
|---|---|---|
| Tested | Unit tests, replay of last 3 months' usage on a copy | Replay diff report. **Not tested:** accounts with mid-month plan changes |
| Rollout | 1% (internal + 20 friendly accounts) → 10% → 100%, 48 hours each | Move-on: zero invoice variance above 0.5% |
| Monitoring | Invoice variance, support tickets tagged billing | Watcher: finance ops, daily for 7 days |
| Rollback | Flag off; credit-note script ready | **Not rehearsed.** Hold until rehearsed |
| Support | Billing FAQ + escalation to finance ops | Support lead briefed |
| Dependencies | Finance month-end close Day 28-3 | Ship on Day 8, off the close window |
## Go / hold criteria
| # | Criterion | Threshold | Type |
|---|---|---|---|
| 1 | Replay variance | < 0.5% on every tested account | Must-pass |
| 2 | Rollback rehearsed | Credit-note script run on a copy | Must-pass |
| 3 | Mid-month plan-change accounts | Manually checked for 10 | Watch |
## Decision
**Hold** until criterion 2 is met (one day). Then go to the 1% stage. Decided by: VP Product.
```
## What to learn from this
- **A small change got the heavy check** because the cost of a wrong invoice is trust.
- **The unrehearsed rollback caused the hold,** a one-day delay instead of a billing incident.
- **The release avoided the finance close window,** which no test would have shown.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |