agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/team-release/SKILL.md

team-release

Skill9 starsChanged 7 months agoMITView on GitHub

Multi-agent orchestration for publishing a release. Coordinates release-manager, qa-lead, exploit-security-specialist, performance-analyst, community-manager, and writer.

18 other projects use a version of this.

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

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    qa-lead: Verify test plan completion

    line 13
  2. Distinctive:

    release-manager: Verify experience configuration (icon, thumbnails, description, social links)

    line 24
  3. Distinctive:

    devops-engineer: Verify CI/CD and deployment pipeline ready

    line 25
  4. Distinctive:

    release-manager: Verify new version is live

    line 29
  5. Very specific:

    Run /publish-review (comprehensive checklist)

    line 45
  6. Distinctive:

    Verify all metrics targets met

    line 47
  7. Distinctive:

    Verify all Roblox experience settings

    line 55
  8. Distinctive:

    Ensure CI/CD is ready

    line 56
  9. Distinctive:

    Verify rollback plan is documented

    line 57
  10. Distinctive:

    Verify new version running

    line 71

“Common” is measured: kept by at least 6 in 10 of the 16 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

/team-release — Release Publishing Team

Orchestration Flow

Releases involve many disciplines. This orchestrates them into a publish.

Phase 1: Verification

  1. qa-lead: Verify test plan completion
  2. exploit-security-specialist: Final security pass
  3. performance-analyst: Final perf benchmarks
  4. release-manager: Runs /publish-review checklist

Phase 2: Documentation

  1. release-manager: Generate /changelog
  2. writer: Polish technical changelog into player-facing /patch-notes
  3. community-manager: Prep Discord / social announcements

Phase 3: Configuration

  1. release-manager: Verify experience configuration (icon, thumbnails, description, social links)
  2. devops-engineer: Verify CI/CD and deployment pipeline ready

Phase 4: Publish

  1. release-manager: Execute publish
  2. release-manager: Verify new version is live
  3. community-manager: Publish community announcements

Phase 5: Monitor

  1. analytics-retention-specialist: Watch metrics dashboards
  2. qa-lead: Watch bug reports
  3. incident-responder-style workflow: Ready for hotfix if needed

Steps

1. Gather Context

  • "What version?" (X.Y.Z)
  • "What's the theme?"
  • "What's the rollout strategy?" (immediate / gradual / canary)

2. Verification Phase

  • Run /publish-review (comprehensive checklist)
  • Any critical blockers → halt release until resolved
  • Verify all metrics targets met

3. Documentation Phase

  • Generate changelog
  • Polish into patch notes
  • Draft community announcements

4. Configuration Phase

  • Verify all Roblox experience settings
  • Ensure CI/CD is ready
  • Verify rollback plan is documented

5. Go/No-Go Decision

Present the full situation to the user:

  • Verification status
  • Documentation ready
  • Configuration ready
  • Monitoring set up
  • Rollback plan

User makes the final go/no-go call.

6. Publish Phase

  • Execute publish (via Studio or Open Cloud)
  • Verify new version running
  • Send announcements
  • Start monitoring

7. First 24 Hours

  • Team on call
  • Watch crash rate, error rate, retention, revenue
  • Respond to any issues via /hotfix if needed

Output

A successful release with documentation, monitoring, and communication.

Blockers (halt release)

  • S0 bug discovered in verification
  • Performance regression vs. baseline
  • Critical security finding
  • DataStore migration untested
  • Rollback plan not documented
  • Team not ready for launch support

Quality Checks

  • All phases completed
  • User explicitly approved go/no-go
  • New version verified live
  • Monitoring active
  • Communications sent

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.