publish-release-documentation — Claude Code command: what it does
publish-release-documentation turns a version, a list of audiences and a deadline into a release documentation packet: notes, a changelog entry and a workback tracker.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/publish-release-documentation.mdWhat publish-release-documentation does
You call /technical-writing:publish-release-documentation with a version, the audiences who need the news, the channels to publish in and a target date. Out comes the paperwork for a launch: release notes, a changelog line, an enablement summary.
The flow has five stages. Feature intake gathers the list, risk notes and screenshots; an artifact plan then decides which asset goes to which audience and channel. A workback schedule hands out owners and review checkpoints. A quality pass covers style, accuracy, accessibility and localization, and the final stage pushes to the doc portal and status page and logs the changelog entry.
Four helpers carry the work: release-documentation-manager runs the flow and approvals, documentation-architect keeps it inside governance rules, and the quality-review-checklist and versioning-dashboard skills cover QA and version support data. Those agents and skills have to exist in the project, otherwise the command is just a list of steps in a markdown file.
What it helps with
- draft release notes and a changelog entry before launch day
- map which assets each audience and channel needs
- assign owners and review checkpoints on a workback schedule
- run style, accessibility and localization checks with sign-off
- push updates to the docs portal and status page
Example prompts for the agent
- /technical-writing:publish-release-documentation --release "2026.2" --audiences developers,admins,cs --channels docs,email,in-app --deadline 2025-12-15
- /technical-writing:publish-release-documentation --release "2026.2" --audiences partners --channels community,enablement --locales en,es
- Run
/technical-writing:publish-release-documentationfor2026.2and show me the tracker with task owners.
How to install publish-release-documentation
Manually: put the files in place
.claude/commands/publish-release-documentation.mdCall it with /publish-release-documentation. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/publish-release-documentation.mdCall it with /prompts:publish-release-documentation. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/publish-release-documentation.prompt.mdManually: put the files in place
.gemini/commands/publish-release-documentation.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about publish-release-documentation
How do I install publish-release-documentation in Claude Code?
Copy the command file to .claude/commands/publish-release-documentation.md in your project. That one file is the install.
What does publish-release-documentation do?
It runs the launch documentation workflow: collect features and risks, plan artifacts per audience and channel, build a workback schedule with owners, review quality, then publish and log the changelog entry.
Which arguments does the command take?
--release, --audiences, --channels and --deadline; --locales is optional and covers localization needs.
Source text
publish-release-documentation.md · Apache-2.0
--- name: publish-release-documentation description: Coordinates release notes, changelog, and enablement updates for a launch. usage: /technical-writing:publish-release-documentation --release "2026.2" --audiences developers,admins,cs --channels docs,email,in-app --deadline 2025-12-15 --- # Command: publish-release-documentation ## Inputs - **release** – version identifier or codename. - **audiences** – comma-separated (developers, admins, cs, marketing, exec, partners). - **channels** – docs, email, in-app, community, enablement. - **deadline** – target publication date. - **locales** – optional localization requirements (en, es, jp, etc.). ## Workflow 1. **Feature Intake** – capture feature list, risk notes, screenshots, approvals needed. 2. **Artifact Plan** – map which assets are needed per audience/channel. 3. **Workback Schedule** – assign owners, deadlines, and review checkpoints. 4. **Quality Review** – enforce style, accuracy, accessibility, and localization steps. 5. **Publishing & Notification** – push updates to doc portals, status pages, comms channels; log changelog entry. ## Outputs - Release communication packet (notes, changelog, enablement summary). - Workback tracker with task status and owners. - QA + localization checklist with sign-offs. ## Agent/Skill Invocations - `release-documentation-manager` – orchestrates workflow + approvals. - `documentation-architect` – ensures governance compliance. - `quality-review-checklist` skill – enforces QA + accessibility steps. - `versioning-dashboard` skill – updates version support + retirement info. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents