launch-checklist
Skill152 starsChanged 8 months agoMITView on GitHub
Pre-Launch - [ ] Feature complete and QA'd - [ ] Rollback plan documented and tested - [ ] Success metrics defined with baselines - [ ] Monitoring dashboards set up - [ ] Support team briefed with FAQ - [ ] Release notes drafted - [ ] Feature flag configured (if gradual rollout) Launch Day - [ ] Deploy during low-traffic window - [ ] Verify metrics are tracking - [ ] Monitor error rates for 2 hours -…
26 other projects use a version of this.
Adopted by
Most recently taken up by
- getpaidskills/skillstheir own version, first seen Nov 8, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- fullstackinnoAI/skillstheir own version, first seen Nov 1, 2026
- munnam77/claude-for-solopreneurstheir own version, first seen Oct 20, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Oct 19, 2026
- venus2099/codex-game-studiostheir own version, first seen Oct 17, 2026
Used with
Projects with it also use patch-notes, asset-audit 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.
CoralGameSkillpatch-notes
Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.
Also in 4 projects that use this
- CoralGameSkill
asset-audit
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
Also in 4 projects that use this
- +10 more from CoralGame
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- hamzafarooq/claude-code-starter★ 145same name
- striderZA/OpenCodeGameStudios★ 118same name
- Mehdibargach/claude-code-pm-skills★ 97same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- aroyburman-codes/pm-skills★ 25same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- dawn840705/codex-code-studios★ 17same name
16 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 repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- competitive-analysisSkill
- metrics-definerSkill
- prd-writerSkill
- sprint-plannerSkill
- user-researchSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
4
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
- Distinctive: line 67
Every item needs an owner and a deadline.
- Distinctive: line 68
Never launch on Friday afternoons
- Distinctive: line 69
If rollback takes more than 5 minutes, add more testing time
- Distinctive: line 70
Every item must be verifiable.
“Common” is measured: kept by at least 6 in 10 of the 21 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
Launch Checklist
Trigger
Activate on "launch checklist", "pre-launch check", "ready to launch?", "launch prep".
Behavior
Step 1: Get Context
Ask:
- What are you launching?
- Launch date
- How many users affected?
- Risk level (high/medium/low)
Step 2: Generate Checklist
Pre-Launch
- Feature complete and QA'd
- Rollback plan documented and tested
- Success metrics defined with baselines
- Monitoring dashboards set up
- Support team briefed with FAQ
- Release notes drafted
- Feature flag configured (if gradual rollout)
Launch Day
- Deploy during low-traffic window
- Verify metrics are tracking
- Monitor error rates for 2 hours
- Send internal launch comms
- Publish release notes
Post-Launch (48 hours)
- Check primary metric vs baseline
- Check guardrail metrics
- Review support tickets for new issues
- Share initial results with team
Post-Launch (1 week)
- Full metrics review
- Ship or iterate decision
- Retrospective if needed
Risk Scaling
Scale the checklist to risk level:
| Risk Level | When | What to Add |
| Low | Config change, copy update, small UI tweak | Minimal — deploy, monitor for 30 min, done |
| Medium | New feature behind flag, migration with rollback | Full checklist above. 2-hour monitoring window |
| High | Pricing change, auth flow, data migration, public-facing API | Everything above PLUS: staged rollout (1% → 10% → 50% → 100%), war room channel, exec notification, 24-hour monitoring |
Example: Good vs Bad Launch Checklist Items
Bad: "Make sure everything works" Good: "Verify signup flow completes end-to-end in staging (email → verification → first dashboard load). Test with Gmail, Outlook, and corporate SSO."
Bad: "Tell the team" Good: "Post in #eng-launches: what shipped, who's on-call, rollback command, link to monitoring dashboard."
Bad: "Watch metrics" Good: "Monitor error rate in Datadog for 2 hours post-deploy. Baseline: 0.3%. Alert threshold: 0.5%. Rollback threshold: 1.0%."
Rules
- Higher risk = more checklist items. Scale accordingly.
- Every item needs an owner and a deadline. Not "soon" — a time.
- Never launch on Friday afternoons
- If rollback takes more than 5 minutes, add more testing time
- Every item must be verifiable. "Done" means someone can confirm it, not just feel it.
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.