agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/launch-checklist/SKILL.md

launch-checklist

Skill9 starsChanged 7 months agoMITView on GitHub

First launch specific checklist. Soft launch plan, metrics to watch, and go/no-go criteria. Use for the first public launch of a new Roblox game.

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use team-level.

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.
  • CoralGameSkill

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 3

    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:

    Verify issue (reproduce or confirm from multiple reports)

    line 80
  2. Very specific:

    If hotfixable: run /hotfix workflow

    line 82
  3. Distinctive:

    If not: consider rollback via Studio version history

    line 83
  4. Distinctive:

    Document for post-launch retro

    line 85

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

/launch-checklist — First Launch Preparation

Delegate to: release-manager (with producer, analytics-retention-specialist, community-manager)

Unique to First Launch

First launches are higher-risk than updates — no existing player base to forgive bugs, and a bad first impression is hard to recover from. This checklist goes beyond /release-checklist with launch-specific considerations.

Phases

Phase 1: Soft Launch (Private Testing)

  • Closed beta with ~50-200 testers
  • Group invite-only or private server code
  • Collect feedback via structured form
  • Monitor crash rate, FPS, feedback quality
  • Iterate on top 3 issues before public launch

Phase 2: Limited Public (Optional)

  • Public but unadvertised — soft launch to see organic discovery
  • Watch Discover page performance
  • Verify critical metrics hold up at higher concurrency
  • Fix any issues found in limited public before full marketing push

Phase 3: Marketing Push

  • Content creator outreach kicks off
  • Social media campaign active
  • Paid ads running (if budget)
  • Community events scheduled
  • Launch trailer published

Phase 4: Launch Day

  • All hands on deck for first 4-8 hours
  • Real-time monitoring in place
  • Quick-response plan for critical bugs
  • Player support active (Discord mods)
  • Press/community engagement

Critical Go/No-Go Criteria

Go Criteria (all must be true)

  • No S0 bugs open
  • No S1 bugs affecting core loop
  • Crash rate < 1% in soft launch
  • D1 retention in soft launch > 20% (prefer 25%+)
  • Average session length > 10 minutes in soft launch
  • Server costs manageable at projected launch CCU
  • Team ready for launch-day support
  • Rollback plan tested

No-Go Triggers

  • Any S0 bug discovered in final testing
  • Crash rate > 2% in soft launch
  • DataStore failures > 0.5% of operations
  • Server crashes > 5% of sessions
  • Team burnout / not ready for launch support
  • Competitive release same day (potential to delay)

Launch Day Monitoring

Metrics to Watch (First 4 Hours)

  • CCU: Real-time concurrent users
  • Join Rate: New players per minute
  • Session Length: First-session duration
  • Crash Rate: Client/server crashes
  • Error Rate: Script errors
  • DataStore Errors: Save/load failures
  • Revenue: ARPDAU, conversion rate (if monetization enabled)

Alert Thresholds (trigger immediate response)

  • CCU drops > 50% in 15 minutes
  • Crash rate > 5%
  • DataStore error rate > 1%
  • Player reports > 10 of same issue

Response Protocol

  1. Verify issue (reproduce or confirm from multiple reports)
  2. Classify severity
  3. If hotfixable: run /hotfix workflow
  4. If not: consider rollback via Studio version history
  5. Communicate to community (Discord, Twitter)
  6. Document for post-launch retro

Output

# Launch Checklist: [Game Name]

**Target Launch Date**: YYYY-MM-DD
**Soft Launch Date**: YYYY-MM-DD
**Phase**: [Planning / Soft Launch / Public Limited / Marketing / Launch / Post-Launch]

## Go/No-Go Status
- Critical criteria: [X/Y met]
- **Recommendation**: [Go / Delay / Reset Soft Launch]

## Monitoring Setup
- Dashboards: [list]
- Alerts: [list]
- On-call: [who]

## Communication Plan
- Discord: [announcement ready?]
- Twitter: [post schedule?]
- Creators: [notified?]

## Risk Register
1. [Top launch risk]
2. [Top launch risk]

## Next Steps
1. [Immediate action]
2. [Immediate action]

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.