launch-readiness
Skill3 starsChanged 18 days agoMITView on GitHub
Help PMs ensure launches are well-planned with nothing falling through the cracks. Use before any feature launch, experiment rollout, or release.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- harrison-ming/chuhai-skillstheir own version, first seen Nov 8, 2026
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- omdenkar2-ui/all-in-onetheir own version, first seen Nov 1, 2026
- Hyde-and-Larkin/product-marketing-toolkittheir own version, first seen Nov 1, 2026
- vindreshsingh/engineering-skillstheir own version, first seen Oct 20, 2026
- leymish01-oss/claude-code-founder-skills-sampletheir own version, first seen Oct 20, 2026
Other versions13 projects use a version of this.
Word for word · 1
- ianklassen/ai-pm-system★ 1100% same
Edited · 0
None found.
Wrote their own version · 12
- pratikshadake/claude-product-management-skills★ 33same name
- RizwanZafaris/product-manager-OS★ 4same name
- Hyde-and-Larkin/product-marketing-toolkit★ 2same name
- paureis/pau-skills★ 2same name
- AndyMelnykov/pm-loops★ 1same name
- harrison-ming/chuhai-skills★ 1same name
- janellecipriano/pm-skills★ 1same name
- mikezamayias/agent-skills★ 1same name
- ejwhite7/product-release-checklist★ 0same name
- leymish01-oss/claude-code-founder-skills-sample★ 0same name
2 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 repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- company-product-signalsSkill
- company-researcherSkill
- company-strategySkill
- pm-os-onboardingSkill
- brainstormingSkill
- continual-learningSkill
- decision-loggerSkill
- eval-briefSkill
- exec-communicatorSkill
- experiment-designerSkill
- experiment-writeupSkill
- knowledge-updaterSkill
- launch-postSkill
- meeting-to-actionsSkill
- one-pagerSkill
- pptx-creatorSkill
- prd-writerSkill
- stakeholder-updateSkill
- strategy-connectorSkill
- what-ifSkill
- working-backwardsSkill
- writing-clearlySkill
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 9 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 12
Before a feature launch
- Distinctive: line 13
Before an experiment rollout
- Distinctive: line 14
Before a product release
- Distinctive: line 16
When asked "are we ready to launch?"
“Common” is measured: kept by at least 6 in 10 of the 9 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 Readiness
Help PMs run launch readiness checklists and make go/no-go recommendations. Ensures launches are planned, risks are surfaced, and stakeholders are aligned.
When to Use
- Before a feature launch
- Before an experiment rollout
- Before a product release
- Go/no-go meeting prep
- When asked "are we ready to launch?"
Process / Template
1. Define Launch Scope
- What is being launched? (feature, experiment, release)
- Target audience and rollout plan (% of users, segments)
- Launch date and any phased milestones
2. Run the Checklist
Product & Quality
- All P0/P1 bugs resolved or accepted
- Acceptance criteria met
- Edge cases and error states handled
- Rollback plan documented
Technical
- Feature flags / kill switches in place
- Monitoring and alerting configured
- Performance and load tested (if applicable)
- Data pipeline or analytics verified
Legal, Compliance, Security
- Legal review complete (if required)
- Privacy/compliance checks done
- Security review (if applicable)
Go-to-Market
- Support team briefed and docs updated
- Customer-facing comms ready (if applicable)
- Internal launch post drafted
Stakeholders
- Key stakeholders informed
- Escalation path defined
- Post-launch review scheduled
3. Assess Risks
- What could go wrong?
- Mitigation in place?
- Acceptable residual risk?
4. Make Go/No-Go Recommendation
| Status | Criteria |
| Go | All critical items green, risks acceptable |
| Conditional Go | Minor items open; launch with monitoring |
| No-Go | Critical gaps; delay until resolved |
5. Document Decision
- Summary of checklist outcome
- Open items and owners
- Go/no-go recommendation with rationale
- Next steps (if no-go or conditional)
Output
A Launch Readiness Summary including:
- Checklist status (green/yellow/red per area)
- Risk assessment
- Go/no-go recommendation
- Open items with owners
- Post-launch plan (monitoring, review)
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.