Index of every page on this site: llms.txt
All skills
deanpeters avatar

/release-readiness

@476ae12
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/release-readiness

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplessample.md

≈515 tokens on demand. Your agent reads this file only when SKILL.md points to it.

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.


## 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts7d3 checks · Risk SAFE
  • Gen Agent Trust Hub7d

    The skill provides a framework and templates for release readiness checks. No security risks were identified as the skill contains only markdown-based process guidelines and lacks executable code or network operations.

  • Socket7d

    No alerts

  • Snyk7d

    Risk: LOW · No issues

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[what is shipping, to whom, and how reversible it is]
type
component
theme
pm-artifacts
Other metadata
intent
A right-sized readiness check for shipping a release (a deploy, a firmware update, a configuration change), distinct from the business launch. Confirms what changed, how it's tested, how it rolls out, how it's watched, how it is undone, and who is ready to support it, with a go / hold decision made on criteria agreed before looking at status. Sized to the blast radius and reversibility.
best_for
[
  "Deciding go or hold on a release with criteria agreed beforehand",
  "Making rollback, monitoring, and support ready before shipping, not after",
  "Sizing the check to what a failure would cost and how reversible it is",
  "Separating the technical release from the business launch"
]
scenarios
[
  "We ship Thursday. What do we need to confirm before we hit go?",
  "Release is a pricing-engine change that touches billing. How careful should we be?",
  "Firmware update to 2,000 field units. What does 'ready' mean?",
  "Write the go/hold criteria for a low-risk UI change"
]
estimated_time
20-30 min

README badge

README badge for deanpeters/product-manager-skills/release-readiness