release-checklist
Skill9 starsChanged 7 months agoMITView on GitHub
Full release checklist (more comprehensive than publish-review). Includes marketing prep, community comms, and post-release monitoring setup.
33 other projects use a version of this.
Adopted by
Most recently taken up by
- Lethe044/agentskill-kittheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- erikdarlingdata/PerformanceMonitortheir own version, first seen Nov 11, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- TrueImmortal82/open-code-skillstheir own version, first seen Nov 8, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
Used with
Projects with it also use playtest-report, soak-test and 9 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.
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 12 projects that use this
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 9 projects that use this
lilangMaxSkillteam-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 9 projects that use this
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 12 projects that use this
- +4 more from lilangMax
- +3 more from CoralGame
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- maximhq/bifrost★ 9.6ksame name
- tsukumijima/KonomiTV★ 1.1ksame name
- erikdarlingdata/PerformanceMonitor★ 536same name
- nkarasiak/qgis-mcp★ 364same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- tranhieutt/software_development_department★ 71same name
- Lethe044/agentskill-kit★ 50same name
- cenconq25/claude-code-app-studio★ 40same name
23 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
- 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-releaseSkill
- team-uiSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
The file
Files
/release-checklist — Full Release Checklist
Delegate to: release-manager (with producer for coordination)
Use When
- Major version release (1.0 → 2.0, etc.)
- Minor release with significant features
- Milestone ship with public announcement
Checklist
Pre-Release (1-2 weeks out)
- Feature freeze confirmed
- All features tagged for this release frozen
- Hotfix criteria documented (what warrants a post-release patch)
- Regression testing plan drafted (delegate to qa-lead)
- Performance benchmarks re-run (delegate to performance-analyst)
- Security audit complete (delegate to exploit-security-specialist)
- DataStore migration tested (if schema changed)
Code & Content (1 week out)
- All critical bugs resolved
- All S0/S1 bugs from bug tracker resolved
- Code review complete on release branch
/luau-lintpasses without errors/code-reviewpasses- No
print()or debug code in production paths - All TODO items for this release closed
Experience Configuration (1 week out)
- Game icon finalized (512×512)
- Thumbnails updated (up to 10, 1920×1080)
- Description updated (key features, call to action)
- Genre tags reviewed
- Max players validated
- Social links active (Discord, Twitter, YouTube)
- Age guidelines appropriate
Marketing & Communication (1 week out)
- Patch notes drafted (
/patch-notes) - Trailer/teaser ready (if major release)
- Social media posts scheduled
- Discord announcement prepared
- Content creators notified (for major releases)
- Press kit updated (if applicable)
Release Day (T-0)
- Final smoke test on production branch
- DataStore backup confirmed (manual or via backup mechanism)
- Team monitoring set up
- Publish to Roblox (
/publish-reviewchecklist complete first) - Verify first server is running new version
- Social media posts published
- Community announcement published
Post-Release (0-24 hours)
- Crash rate monitored (< 1% target)
- Error rate monitored
- Player feedback channels monitored (Discord, in-game chat)
- CCU trends watched
- DataStore error rate watched
- Revenue metrics watched (if applicable)
Post-Release (24-72 hours)
- Formal incident review if any S0/S1 bugs occurred
- Retrospective scheduled
- Player feedback triaged
- Hotfix needed? Decide and execute via
/hotfix
Post-Release (1 week)
- Retention metrics checked (
/retention-analysis) - Engagement metrics checked
- Revenue metrics checked (if applicable)
- Document learnings in
production/releases/<version>-learnings.md
Output
Generate full checklist with status for each item:
# Release Checklist: v[X.Y.Z]
**Target Release Date**: YYYY-MM-DD
**Release Lead**: [user]
**Status**: [Planning / Preparing / Ready / Released / Post-Release]
[Full checklist with pass/fail for each item]
## Open Items
1. [Blocker]
2. [Blocker]
## Ready for Release?
[✅ Yes / ⏸️ No, pending items above]Save to production/releases/checklist-<version>.md on approval.
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.

