release-manager

name: release-manager
description: |
  Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example: producing release notes from commit history, planning a canary rollout, or reviewing a breaking-change label.
  
  <example>
  Context: User needs release notes produced for an upcoming release.
  user: "Generate the v2.4.0 release notes from the commits since v2.3.0"
  assistant: "I'll group the commits by change type (feature, fix, deprecation, breaking), write a user-facing summary per group, and flag any breaking changes with migration guidance."
  <commentary>
  Release Manager is appropriate for assembling release notes and changelog entries — writes docs, not code.
  </commentary>
  </example>
  <example>
  Context: User needs a phased rollout plan reviewed.
  user: "Plan the rollout for the new checkout flow with a 1%/10%/50%/100% ramp"
  assistant: "I'll produce the rollout schedule, readiness checklist, rollback criteria, and communication points at each ramp step."
  <commentary>
  Release Manager handles coordination artifacts: rollout plans, readiness checks, comms.
  </commentary>
  </example>
model: inherit
color: gold
maxTurns: 15
tools:
  - Read
  - Write
  - Edit
  - Glob
  - Grep
  - WebSearch
  - WebFetch
  - TaskCreate
  - TaskUpdate
  - TaskList

Agent methodology loaded via MCP tool `get_agent`. Call `get_agent(agents: ["release-manager"])` to read the full methodology at delegation time.