SkillAgentSearch skills...

release-readiness

Check a release is safe to ship: tests, rollout, monitoring, rollback, support

Install / Use

npx skills add deanpeters/Product-Manager-Skills --skill release-readiness

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Category

Operations

Supported Platforms

Zed

Tags

Our assessment of release-readiness

release-readiness scores 85/100 on our quality scale, 515th of 745 Operations skills we index.

Its SKILL.md is 10 KB long, well organised into 30 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
13/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so release-readiness is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

release-readiness compared with similar skills

All 4 of these similar skills score higher than release-readiness; compare them before choosing.

SkillScoreStarsUpdatedFormat
release-readiness (this skill)by deanpeters857.1k3mo agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install release-readiness?
Run npx skills add deanpeters/Product-Manager-Skills --skill release-readiness. The install tabs above show the steps for each supported agent.
Which AI agents does release-readiness work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is release-readiness safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is release-readiness still maintained?
The repository was last updated about 3 months ago, so release-readiness is actively maintained.

name: release-readiness argument-hint: "[what is shipping, to whom, and how reversible it is]" description: "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." 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. type: component theme: pm-artifacts 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"

Release Readiness

Purpose

Decide whether a release is safe to ship, with a check sized to what a failure would cost. The output is a short readiness record: what is changing, how it was tested, how it rolls out, how it is watched, how it is undone, who will support it, and a go / hold decision made against criteria the team agreed before looking at the status.

The sentence to keep in your head: before you ship, know how you'd undo it. A release you can't reverse needs a higher bar than one you can undo in a minute.

This is the technical release check. The business launch (sales, support, marketing, partners) is launch-plan. A feature can release quietly many times before it launches, and a launch can sit on one release.

Input

Works best with: What is shipping, who it reaches, and how reversible it is.

Also useful: The test results, the rollout plan, the monitoring in place, the rollback method, and who is on call or in support.

Anything supplied with the invocation itself (text after the skill name, a pasted context dump, or an appended ARGUMENTS: line) counts as answers already given. Use it and skip whatever it covers; don't re-ask.

Arriving empty-handed? That works too. The skill asks what's shipping and how bad a failure would be, picks a level, and builds the check from your answers. Anything unknown becomes a labeled blank ([NEEDS SOURCE]), never an assumed yes.

Example invocations:

  • Release: a change to how overage is billed. Reaches all paying accounts. Rollback is a flag.
  • Firmware 2.1 to 2,000 field units over the air. No physical rollback once flashed.

Key Concepts

Right-Size the Check (the Level Dial)

Not every release needs the same care. Pick a level, say why in one line, and let the team move it:

| | Level 1: Light | Level 2: Standard | Level 3: Heavy | |---|---|---|---| | Typical release | Small, reversible, narrow (copy, minor UI, internal tool) | A normal feature or fix to real customers | Billing, security, data migrations, firmware or hardware in the field, regulated | | Checks | Tested, rollback known, one owner | + staged rollout, monitoring, support briefed | + formal go/hold, rehearsed rollback, incident owner, comms ready | | Output feel | A few lines | One-page record | Full record with sign-offs |

Level 2 is the default. Never default to Level 3. A heavy ritual for a copy change teaches the team that readiness is ceremony, and they'll skip it on the day it matters. If they go lighter, name what is left uncovered.

Blast Radius and Reversibility Set the Level

Two questions decide: how many people (or units) does it reach, and how fast and cleanly can it be undone? A feature flag on 1% of accounts is cheap to reverse. A database migration or an over-the-air flash with no physical rollback is not. High reach plus hard reversal is Level 3.

The Seven Checks

  1. What changes. A plain description, and what does not change (so nobody assumes).
  2. How it was tested. What was tested, in what environment, and what was not tested.
  3. Rollout. Staged (a small share first, then more) rather than all at once, and the criteria for moving to the next stage.
  4. Monitoring. The signals that say it's working or failing (errors, latency, support volume, failure rates), who watches them, and for how long.
  5. Rollback. The exact way to undo it, how long it takes, and whether it's been tried. "We would revert" is not a rollback plan.
  6. Support and communication. Who is ready to take the calls, what they know, and what customers are told if something breaks.
  7. Dependencies and timing. Other systems or teams affected, and why now (not a Friday afternoon or a customer's peak week).

Go / Hold Criteria Are Agreed First

Decide before the status is known what counts as must-pass (tests green, rollback rehearsed) and what is watch-only. A go/hold made after looking at a mixed picture gets talked into "go." Hold is a legitimate and cheap outcome compared to a bad release.

Not Only Software

For firmware, hardware, or service changes the same seven checks apply, with physical specifics: which units, which firmware versions, whether a field rollback exists, whether certification is affected, and who handles units that fail mid-update.

Facilitation Source of Truth

Use workshop-facilitation as the interaction protocol when running this conversationally.

Default entry mode: Guided · set in pm-skills.config.yaml (library-wide default or a per-skill override); the user's own choice in the session always wins. On the first turn, offer all three modes, then open in the default without waiting for a pick: Guided asks the first question, Context dump invites the paste, Best guess asks for a one-sentence minimum and drafts with every assumption labeled.

Anti-Patterns (what this is NOT)

  • Not the business launch. See launch-plan.
  • Not a code review or QA plan. It checks that testing and rollback exist, not how to test.
  • Not a gate the PM owns. The release owner decides; this skill makes the criteria visible.
  • Not heavy by default. Light is a legitimate level.

Application

Use template.md for the scaffold.

Output convention. Artifact first: the level and why, the seven checks, the go/hold criteria and result, and the open items. Commentary short, after. Every unconfirmed check is [NEEDS SOURCE] or "not confirmed", never assumed done.

If the PM brings a plan, critique first. Is the level justified by reach and reversibility? Is there a rollback that has been tried? Is monitoring tied to named signals and a watcher? Is rollout staged with criteria? Were go/hold criteria written before the status? Name gaps; offer rewrites last.

Step 1: Describe the Release

What changes, what doesn't, who or what it reaches, and how reversible it is.

Step 2: Set the Level

Recommend Light, Standard, or Heavy from reach and reversibility; say why; honor an override and name what a lighter level leaves uncovered.

Step 3: Walk the Seven Checks

For each, record the state and mark anything unconfirmed. Press on rollback: has it been tried?

Step 4: Set Go / Hold Criteria

Must-pass and watch, with thresholds, agreed before reading the status.

Step 5: Decide and Hand Back

State go, hold, or go with conditions, and the open items with owners. Short summary (supplied, inferred, unknown), then a numbered ladder, evidence-favored first, labeled (Recommended): hold until the rollback is rehearsed; ship to a small share first; ship as planned with a named watcher for 48 hours; or reschedule off the peak window.


Examples

See examples/sample.md (Fieldlight billing change, SaaS, Level 3) and examples/sample-industrial.md (Northfield firmware update, industrial, Level 3, ending in a hold).


Common Pitfalls

Pitfall 1: "We'd Just Revert"

Symptom: Rollback is an intention. Consequence: The first time it's tried is during the incident. Fix: Name the method, the time it takes, and whether it was rehearsed.

Pitfall 2: Everything at Once

Symptom: A full rollout on day one. Consequence: Any defect reaches every customer. Fix: Stage it with criteria for moving on.

Pitfall 3: Nobody Watching

Symptom: Monitoring exists; no one is assigned. Consequence: Failure is found by customers. Fix: Name the signals, the watcher, and the duration.

Pitfall 4: Criteria Written After the Status

Symptom: "It's mostly green, let's go." Consequence: Real risks are rationalized. Fix: Agree must-pass and watch criteria first.

Pitfall 5: Heavy by Default

Symptom: A copy change gets a full sign-off. Consequence: The team learns to skip the process. Fix: Size to reach and reversibility.

Pitfall 6: Releasing at the Worst Time

Symptom: A Friday afternoon or a customer's peak week. Consequence: Slow response when it matters. Fix: Name why now, and choose a window when people can respond.


References

Skill Files

Related Skills

External Frameworks

  • Staged rollouts, feature flags, and rollback: standard release-engineering practice.
  • Production readiness reviews: common site-reliability practice (for example Site Reliability Engineering, Google).

Provenance

Distilled from practitioner experience preparing product releases for software and connected hardware.

Related Skills

View on GitHub
GitHub Stars7.1k
CategoryOperations
Updated2mo ago
Forks846

Languages

Shell

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium