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-industrial.md

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

Release Readiness Example: Industrial

Release: firmware 2.1 for NFA-500 controllers, over the air to ~2,000 field units Why this example exists: no physical rollback once flashed, so reversibility is the whole question.


## The release
**What changes:** new fault-detection algorithm and a radio stack update.
**What does not change:** control logic, I/O mapping, certified safety functions.
**Reaches:** ~2,000 field units. **Reversibility:** a failed flash can brick a unit; rollback needs a
site visit.
**Level:** 3 Heavy.

## The seven checks
| Check | State | Evidence |
|---|---|---|
| Tested | Bench, thermal chamber, 30-unit soak for 3 weeks | Test report. **Not tested:** units on the oldest hardware revision (B) |
| Rollout | 20 units → 200 → remainder, 1 week each | Move-on: zero failed flashes and fault rate not above baseline |
| Monitoring | Flash success rate, fault-code volume, hotline calls | Watcher: service lead, daily for 14 days |
| Rollback | Previous image kept in the unit's second bank; auto-revert if boot fails | **Rehearsed on 10 bench units** |
| Support | Hotline briefed; script for "controller offline after update" | Done |
| Certification | Radio stack change checked with the assessment body | **Not confirmed**: pending reply |
| Timing | Avoid plants' scheduled shutdown weeks | Customer calendar reviewed |

## Go / hold criteria
| # | Criterion | Threshold | Type |
|---|---|---|---|
| 1 | Soak test | 0 failures in 30 units | Must-pass |
| 2 | Auto-revert on boot failure | Works on 10 of 10 bench units | Must-pass |
| 3 | Radio stack certification impact | Assessment body confirms no re-evaluation | Must-pass |
| 4 | Hardware revision B units | Tested or excluded from the rollout | Must-pass |

## Decision
**Hold.** Criteria 3 and 4 are open. Exclude revision B from stage 1. Re-decide when the assessment
body replies. Decided by: Engineering director.

What to learn from this

  • The two-bank image made a rollback exist. Without it, this would be a physical visit per unit.
  • The hold named two specific blockers, not a general unease.
  • Excluding hardware revision B is a scoping move, not a delay of the whole release.

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