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.

template.md

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

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

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