staged-rollout SKILL.md skillA
staged-rollout from etr/groundwork is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add etr/groundwork/staged-rollout@git:20260912.480a145Pins git:20260912.480a145 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- etr/groundwork
- Path
skills/staged-rollout/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260912.480a145, committed Sep 12, 2026
- First version recorded
- Jun 22, 2026
- Size
- 4,607 bytes
- Repository stars
- 45
- License
- MIT
Roll out a change in stages behind a feature flag with a monitoring window and a written rollback plan - use before shipping anything user-facing, instead of flipping it on for everyone at once.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Staged Rollout ## Overview A change reaches all users gradually, behind a switch you can flip back, while someone watches the signals. **Big-bang releases convert a small bug into a full outage.** A staged rollout converts the same bug into a contained blip caught at 1% traffic. **Core principle:** Every outward-facing change ships behind a flag, advances in stages with a monitoring window between them, and has a rollback plan written *before* launch — not improvised during the incident. This depends on the change being observable first: see [[instrument-observability]] for the signals the monitoring window watches. ## When to Use - Any user-facing or externally-observable change (new endpoint, UI, behavior change, schema migration) - Risky internal changes where a bad deploy degrades many users at once Skip only for trivially reversible, low-blast-radius changes (a copy fix, an internal doc). When unsure, stage it — the cost is one flag. ## Process 1. **Pre-launch checklist.** Confirm before any traffic shift: - Validation and review already passed (see [[validate]] / [[review-pr]]) - Instrumentation is live and the dashboards read real data …
Read the whole file at its exact version.
How to install
mdr add etr/groundwork/staged-rollout@sha256:8085f1dd6f84f6cbThe line at the top of this page pins the label git:20260912.480a145, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lkp2s2d6ic427lch)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 22, 2026 and Sep 12, 2026, about one every 81 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260912.480a145 latest | 2026-09-12 | 480a145 | 4,607 B | A | view · diff |
| git:20260622.3609064 | 2026-06-22 | 3609064 | 4,080 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4607 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
etr/groundwork · 45 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lkp2s2d6ic427lch GET https://markdownregistry.com/api/v1/resolve?ref=etr/groundwork/staged-rollout GET https://markdownregistry.com/api/v1/blob/8085f1dd6f84f6cb06f7fc101b2c8fdf6f925c26757b78233db94f8b045812ad
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.