What is team-release?

A coordinated workflow for moving a software release from a candidate build to production with release management, quality assurance, DevOps, and production planning.

Use it to prepare release branches, changelogs, regression checks, build artifacts, deployment steps, and stakeholder communication.

It brings testing, deployment automation, versioning, and go/no-go decisions into one reviewed process.

team-release — Skill for Claude Code by tranhieutt

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add tranhieutt/software_development_department --skill team-release

Clone the repo

git clone --depth 1 https://github.com/tranhieutt/software_development_department

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-release/github.svg)](https://agentmods.dev/skills/tranhieutt/software_development_department/team-release)

Your own site

<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/team-release"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-release/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/team-release"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/team-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 912 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00049	$0.00912
Opus 5	$0.00024	$0.00456
Sonnet 5	$0.00010	$0.00182
Haiku 4.5	$0.00005	$0.00091

Measured 8d ago against content hash f4fa29bb76d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

team-release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/team-release/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When this skill is invoked, orchestrate the release team through a structured pipeline.

Decision Points: At each phase transition, use AskUserQuestion to present the user with the subagent's proposals as selectable options. Write the agent's full analysis in conversation, then capture the decision with concise labels. The user must approve before moving to the next phase.

Team Composition

release-manager — Release branch, versioning, changelog, deployment
qa-engineer — Test sign-off, regression suite, release quality gate
devops-engineer — Build pipeline, artifacts, deployment automation
producer — Go/no-go decision, stakeholder communication, scheduling

How to Delegate

Use the Task tool to spawn each team member as a subagent:

subagent_type: release-manager — Release branch, versioning, changelog, deployment
subagent_type: qa-engineer — Test sign-off, regression suite, release quality gate
subagent_type: devops-engineer — Build pipeline, artifacts, deployment automation
subagent_type: producer — Go/no-go decision, stakeholder communication

Always provide full context in each agent's prompt (version number, milestone status, known issues). Launch independent agents in parallel where the pipeline allows it (e.g., Phase 3 agents can run simultaneously).

Pipeline

Phase 1: Release Planning

Delegate to producer:

Confirm all milestone acceptance criteria are met
Identify any scope items deferred from this release
Set the target release date and communicate to team
Output: release authorization with scope confirmation

Phase 2: Release Candidate

Delegate to release-manager:

Cut release branch from the agreed commit
Bump version numbers in all relevant files
Generate the release checklist using /release-checklist
Freeze the branch — no feature changes, bug fixes only
Output: release branch name and checklist

Phase 3: Quality Gate (parallel)

Delegate in parallel:

qa-engineer: Execute full regression test suite. Test all critical paths. Verify no S1/S2 bugs. Sign off on quality.
devops-engineer: Build release artifacts for all target platforms. Verify builds are clean and reproducible. Run automated tests in CI.

Read the full file on GitHub · 86 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago First seen · 86 lines · 49 tokens per session scan A f4fa29bb76d4

Subscribe to this mod's changes

team-release is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 912 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

DevOps and cloud Git and workflow Releases antigravity-skills brainstorming claude claude-skills harness-engineering human-in-the-loop

changelog

Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.

tuliosousapro/SaaS-blueprint · 39 tokens

ship-preflight

Stage ⑤.a Ship sub — release-preflight gate. Runs harnessed release-preflight (read-only: CHANGELOG [Unreleased] non-empty + version + git-clean + tag-absent). A failing gate blocks shipping. Nothing is pushed/published/tagged here.

easyinplay/harnessed · 62 tokens

semantic-versioning

Manages project versioning following Semantic Versioning (SemVer) principles. Calculates increments based on changes and synchronizes version across documentation and metadata. Use when the user asks to "bump the version", "prepare a release", or when the changelog skill calls for a release.

tuliosousapro/SaaS-blueprint · 63 tokens

team-release