agentleFS
Sign inStart free
scotidevscotidev/GameDevStudio/.agents/skills/team-release/SKILL.md

team-release

Skill1 starsChanged 8 months agoMITView on GitHub

Orchestrate the release team: coordinates release-manager, qa-lead, devops-engineer, and producer to execute a release from candidate to deployment.

16 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

6 rules. 5 are common, 1 is distinctive, and 0 are very specific to this project.

  • 5

    Common

    Most of the 13 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

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

    line 8
  2. Common:

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

    line 23
  3. Distinctive:

    Always provide full context in each agent's prompt (version number, milestone status, known issues).

    line 29
  4. Common:

    Verify all strings are translated (delegate to localization-lead if available)

    line 55
  5. Common:

    Run performance benchmarks against targets (delegate to performance-analyst if available)

    line 56
  6. Common:

    producer: Update milestone tracking, communicate to stakeholders

    line 76

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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-lead — 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-lead — 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-lead: 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.

Phase 4: Localization and Performance

Delegate (can run in parallel with Phase 3 if resources available):

  • Verify all strings are translated (delegate to localization-lead if available)
  • Run performance benchmarks against targets (delegate to performance-analyst if available)
  • Output: localization and performance sign-off

Phase 5: Go/No-Go

Delegate to producer:

  • Collect sign-off from: qa-lead, release-manager, devops-engineer, technical-director
  • Evaluate any open issues — are they blocking or can they ship?
  • Make the go/no-go call
  • Output: release decision with rationale

Phase 6: Deployment (if GO)

Delegate to release-manager + devops-engineer:

  • Tag the release in version control
  • Generate changelog using /changelog
  • Deploy to staging for final smoke test
  • Deploy to production
  • Monitor for 48 hours post-release

Phase 7: Post-Release

  • release-manager: Generate release report (what shipped, what was deferred, metrics)
  • producer: Update milestone tracking, communicate to stakeholders
  • qa-lead: Monitor incoming bug reports for regressions
  • Schedule post-release retrospective if issues occurred

Output

A summary report covering: release version, scope, quality gate results, go/no-go decision, deployment status, and monitoring plan.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free