rampstackco/claude-skills / skills/release-management
release-management
VerifiedRun the recurring release cycle that turns merged work into a shipped, communicated release: a stated release model, a version derived from the changes, a release candidate and freeze, a written go/no-go gate, staged rollout with an exercised rollback, a hotfix path, and the changelog and release notes. Use this skill whenever the user wants to cut a release, plan or run a release train, decide what version a release should be, freeze code, hold a go/no-go, write a rollout or rollback plan, ship a hotfix, or write release notes, a changelog entry, or a deprecation notice. Triggers on release, cut a release, release notes, changelog, version bump, semver, calver, what version should this be, release train, code freeze, release candidate, RC, go/no-go, rollout plan, staged rollout, canary, rollback plan, hotfix, deprecation notice, release manager, release captain. Also triggers when the user has a set of merged changes and asks how to ship them or what to tell users, even if they never say release.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 359 B |
| SKILL.md | skill md | 18.4 KB |
| references/example-release.md | markdown | 9.9 KB |
| references/go-no-go-template.md | markdown | 3.2 KB |
| references/hotfix-checklist.md | markdown | 3.4 KB |
| references/release-checklist.md | markdown | 4.9 KB |
| references/release-notes-template.md | markdown | 3.6 KB |
| references/rollout-plan-template.md | markdown | 4.5 KB |
| references/versioning-guide.md | markdown | 5.7 KB |
references/rollout-plan-template.md
View on GitHub# Rollout Plan Template
Fill this before the go/no-go. During the rollout, fill in the results column for each stage as it happens. The finished plan is part of the release record.
This plan stages the release build. For ramping one flagged feature inside it, follow `feature-flagging`. For the deploy commands, follow your runbook (see `launch-runbook`).
---
## Template
```
# Rollout plan: [product] [version]
Candidate: [version]-rc.[N], build [identifier]
Rollout owner: [name]
Rollback owner: [name]
Window: [start] to [expected end], [time zone]
Avoid: [dates and times with no on-call cover, peak business events]
## Watch signals
Signals for the whole release, tied to your service level objectives:
| Signal | Source | Normal range | Stop above or below |
|---|---|---|---|
| [error rate, all requests] | [dashboard link] | [range] | [number, duration] |
| [latency p95, changed endpoints] | | | |
| [key flow success rate, e.g. sign-in, checkout] | | | |
| [support contacts tagged to changed areas] | | | |
Signals for specific changes in this release:
| Change (merged item) | Signal | Stop condition |
|---|---|---|
| [item] | [signal] | [number, duration] |
## Stages
| Stage | Exposure | Who or what | Minimum dwell | Stop condition | Owner | Result |
|---|---|---|---|---|---|---|
| 1. Internal | [staff, test accounts, internal environment on production data] | [how selected] | [time] | Any watch signal past its stop value; any S1 or S2 found | [name] | [passed at HH:MM / halted at HH:MM, signal, value] |
| 2. Canary | [percent of traffic, servers, regions, or users] | [how selected] | [time covering a peak period] | [as above] | [name] | |
| 3. Everyone | 100 percent | All | Through the post-release check | [as above] | [name] | |
Advance only when the dwell time is met and every signal is inside its range. Advancing early is a decision the rollout owner records with a reason.
## Rollback
Method: [redeploy previous artifact / revert / flag off / other]
Previous good version: [version, build identifier]
Steps:
1. [step]
2. [step]
3. [verification that the previous version is serving]
Expected time to complete: [minutes]
Last exercised: [date, result, time taken]
Who can call it: [rollout owner, deputy, on-call]
## Irreversible items
Changes that cannot be undone by the rollback above.
| Item | Why it is irreversible | Plan | Owner |
|---|---|---|---|
| [schema change] | [old column dropped / data rewritten] | [expand then contract: which step this release ships] | |
| [public API field or webhook] | [clients may depend on it once published] | [forward fix only; ship behind a flag until stage 3] | |
| [email, push, invoice] | [already sent] | [send only after stage 3 passes] | |
Write "None" if the list is empty, so the reader knows it was checked.
## Halt log
| Time | Stage | Signal | Value | Action | Decided by |
|---|---|---|---|---|---|
## Handoffs
If a stop condition fires and users are affected: open an incident (see `incident-response`) and hand the rollback decision to the incident lead.
```
---
## Expand then contract, step by step
A schema change that would break the previous version if rolled back ships across several releases. Each release is safe to roll back on its own.
1. **Expand.** Add the new column, table, or field. The old one stays. Old and new code both run.
2. **Dual write.** Ship code that writes to both. Reads still use the old one.
3. **Backfill.** Copy existing data into the new structure. Verify counts.
4. **Switch reads.** Ship code that reads from the new structure. Rolling back returns to reading the old one, which is still current.
5. **Stop old writes.** Ship code that writes only to the new structure.
6. **Contract.** Remove the old structure in a later release, after the switch has held through at least one full release.
Name which step this release ships in the irreversible items table. Only step 6 is truly irreversible, and by then nothing reads the old structure.
---
## Choosing stop conditions
- **Write a number and a duration.** "Error rate above 0.5 percent for 10 minutes," not "error rate looks high."
- **Start from the normal range.** Read the last two weeks of the signal at the same time of day. Set the stop just outside the normal spread.
- **Cover what changed.** A release that touches billing needs a billing signal, not only the overall error rate.
- **Include a human signal.** Support contacts tagged to the changed area catch problems no metric was built for.
- **Decide in advance who can override.** An override is logged with a reason, like a freeze exception.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |