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
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- sametcelikbicak/opencode-teamtheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- venus2099/codex-game-studiostheir own version, first seen Oct 17, 2026
- ShiningPlague/shiningplague-studiotheir own version, first seen Oct 11, 2026
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.
lilangMaxSkillcreate-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
lilangMaxSkillstory-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
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- tranhieutt/software_development_department★ 71same name
- sametcelikbicak/opencode-team★ 69same name
- cenconq25/claude-code-app-studio★ 40same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- dawn840705/codex-code-studios★ 17same name
- lilangMax/ClaudeCodeGameStudios★ 8same name
- hongyuanc/codex-game-studios★ 5same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
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
- Distinctive: line 13
qa-lead: Verify test plan completion
- Distinctive: line 24
release-manager: Verify experience configuration (icon, thumbnails, description, social links)
- Distinctive: line 25
devops-engineer: Verify CI/CD and deployment pipeline ready
- Distinctive: line 29
release-manager: Verify new version is live
- Very specific: line 45
Run /publish-review (comprehensive checklist)
- Distinctive: line 47
Verify all metrics targets met
- Distinctive: line 55
Verify all Roblox experience settings
- Distinctive: line 56
Ensure CI/CD is ready
- Distinctive: line 57
Verify rollback plan is documented
- Distinctive: line 71
Verify new version running
“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.
Files
/team-release — Release Publishing Team
Orchestration Flow
Releases involve many disciplines. This orchestrates them into a publish.
Phase 1: Verification
- qa-lead: Verify test plan completion
- exploit-security-specialist: Final security pass
- performance-analyst: Final perf benchmarks
- release-manager: Runs
/publish-reviewchecklist
Phase 2: Documentation
- release-manager: Generate
/changelog - writer: Polish technical changelog into player-facing
/patch-notes - community-manager: Prep Discord / social announcements
Phase 3: Configuration
- release-manager: Verify experience configuration (icon, thumbnails, description, social links)
- devops-engineer: Verify CI/CD and deployment pipeline ready
Phase 4: Publish
- release-manager: Execute publish
- release-manager: Verify new version is live
- community-manager: Publish community announcements
Phase 5: Monitor
- analytics-retention-specialist: Watch metrics dashboards
- qa-lead: Watch bug reports
- 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
/hotfixif 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
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
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.

