Skip to content

rampstackco/claude-skills / skills/release-management

release-management

Verified

Run 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.

references/go-no-go-template.md

View on GitHub
# Go/No-Go Template

Fill this before the decision meeting. The meeting reads it and decides. It does not gather evidence in the room.

Every criterion is marked **passed**, **failed**, or **not evidenced**. Not evidenced counts as failed. One named person makes the decision.

---

## Template

```
# Go/no-go: [product] [version]

Candidate: [version]-rc.[N], build [identifier]
Release model: [train / continuous / milestone]
Decision owner: [name]
Deputy: [name]
Decision time: [YYYY-MM-DD HH:MM, time zone]
Prepared by: [name], [timestamp]

## Scope
Merged items in this release: [count], from [tracker query or version range]
Impact tags: [n] breaking, [n] feature, [n] fix, [n] internal
Version derivation: [highest impact] -> [major / minor / patch / CalVer increment]

## Criteria
| # | Criterion | Threshold | Evidence (link or attachment) | Status |
|---|---|---|---|---|
| 1 | Tests pass on the candidate build | All required suites green on rc.[N] | [runner summary for this build] | [passed / failed / not evidenced] |
| 2 | New work has test plans with results | Every story and bug fix in scope | [test plan links] | |
| 3 | Open S1 defects | 0 | [defect query] | |
| 4 | Open S2 defects | 0 without a workaround | [defect query, workarounds noted] | |
| 5 | Open S3 and S4 defects | Listed, accepted by the owner | [defect query] | |
| 6 | Rollback verified | Exercised within [your limit] on this deploy path | [date, result, time taken] | |
| 7 | Monitoring in place | Alerts and dashboards for changed areas exist | [links] | |
| 8 | Rollout plan complete | Stages, stop conditions, irreversible items filled | [link] | |
| 9 | Release notes drafted | Every user-facing item has a line; checked against the merged list | [link] | |
| 10 | On-call named | Owner for each stage of the rollout window | [names] | |
| 11 | Freeze exceptions | Each logged with a reason | [exception log] | |

Add rows for your product: accessibility checks, legal review, app store review, data protection review.

## Irreversible items
[List from the rollout plan, with the plan for each. "None" if none.]

## Decision
Decision: [GO / NO-GO]
Decided by: [name]
Reason: [one or two sentences tied to the criteria table]

## If no-go
Blocking criteria: [numbers from the table]
Fix: [what changes]
Owner: [name]
Next candidate: [version]-rc.[N+1], expected [date]
Next decision: [date and time]
Scope change, if any: [items removed from the release and where they go]

## Attendees
[names and roles]
```

---

## Notes on filling it in

- **Evidence is a link or an attachment.** "QA says it is fine" is not evidence. A runner summary, a defect query, or a signed test plan is.
- **Evidence is for this candidate.** A test run on `rc.1` does not cover `rc.2` for the areas the change touched.
- **Thresholds are set before the release.** Changing the threshold in the meeting to get to go is a no-go with extra steps.
- **The decision owner can still say no-go with every row passed.** Write the reason. Unknowns the table does not capture are real.
- **A go with an accepted risk names the risk.** "Go, with S2 #482 open and a documented workaround in the support macro."
- **No-go is a normal outcome.** Record it in the release history like any go. A team that never says no-go is not reading its own gate.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexUnverifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall