plan-launch
Skill1 starsChanged 3 months agoMITView on GitHub
Plan a release/launch — choose a rollout strategy, build the cross-functional readiness checklist, set success and guardrail metrics with thresholds, and define Go/No-Go and rollback. Use before shipping a notable change. Dispatches the release-manager.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- konglong87/superPMtheir own version, first seen Mar 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- konglong87/superPM★ 84same name
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 repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-business-caseSkill
- build-roadmapSkill
- capture-feedbackSkill
- close-projectSkill
- coordinate-programSkill
- define-metricsSkill
- define-strategySkill
- design-dashboardSkill
- elicit-requirementsSkill
- groom-backlogSkill
- make-deliverableSkill
- manage-changeSkill
- manage-resourcesSkill
- plan-capacitySkill
- plan-portfolio-automationSkill
- plan-projectSkill
- plan-sprintSkill
- powerbiSkill
- prioritizeSkill
- review-okrsSkill
- review-portfolio-intakeSkill
- run-ceremonySkill
- run-discoverySkill
- run-gate-reviewSkill
- setup-pmoSkill
- track-financialsSkill
- track-portfolioSkill
- track-statusSkill
- write-prdSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 9
Before releasing/launching a notable feature or product.
- Very specific: line 36
Start from templates/launch-plan.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/plan-launch — Ship safely, drive adoption
When to use
Before releasing/launching a notable feature or product; planning a go-to-market motion.
Dispatches
release-manager (lead) + product-analyst (success/guardrail metrics). Consult comms-lead for
announcements; project-manager/program-manager for cross-team coordination.
Inputs
knowledge/roadmap.md, relevant PRDs, knowledge/product-context.md, knowledge/cadence.md.
Steps
- Separate the release (deployment) from the launch (GTM motion); plan both. Confirm the phase gate is passed (go/kill/hold) before committing launch spend.
- Choose a rollout strategy that minimizes blast radius and still yields a real signal (phased/canary/flags).
- Agree the positioning & messaging platform once; match launch strategy to market type (create demand in a new category vs. capture it in an existing one).
- Build the cross-functional readiness checklist (product, eng, quality/security, support, marketing, sales/CS, legal); ensure demand generation and sales/channel enablement are ready before launch day; tier launch effort to impact.
- Define success and guardrail metrics with thresholds before launch; decide expand/hold/rollback rules.
- Name a Go/No-Go owner and a clear rollback trigger; plan the post-launch review (and, for sunsets, an end-of-life plan).
Methods
knowledge/methods/launch-and-gtm.md, knowledge/methods/metrics-and-experimentation.md,
knowledge/methods/project-management.md.
Output
Start from templates/launch-plan.md. Save a launch/release plan + readiness checklist artifact (e.g.,
knowledge/launches/<YYYY-MM-DD>-<name>.md);
log Go/No-Go and rollout decisions to knowledge/decision-log.md. Follow standards/document-standards.md.
Created by Colin Beck<br>
LinkedIn: https://www.linkedin.com/in/beckcolin/<br>
GitHub: https://github.com/link7373
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.