launch-plan
Skill3 starsChanged 8 months agoMITView on GitHub
Build a coordinated product/marketing launch plan with messaging, assets, milestones, instrumentation, and post-launch review.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- deanpeters/Product-Manager-Skillstheir own version, first seen Nov 15, 2026
- 2104178150-ai/megaphonetheir own version, first seen Oct 20, 2026
- kitloomlk-stack/marketing-seo-kittheir own version, first seen Oct 15, 2026
- agentmart/pm-ostheir own version, first seen Oct 15, 2026
- duncan-buildroom/profit-room-skillstheir own version, first seen Oct 13, 2026
- duncan-buildroom/freeskillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use offer-builder.
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.
duncan-buildroomSkilloffer-builder
Build a Hormozi-style "Grand Slam Offer" so good people feel stupid saying no — engineered around the Value Equation (bigger dream outcome, higher belief it'll work, less time, less effort). Use this when the user says "build my offer", "make my offer irresistible", "help me package what I sell", "I don't know how to price/pitch this", "grand slam offer", "I built a product but nobody's buying", or when they have a thing to sell but no compelling way to present it. Push to run this before they try to sell anything.
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- deanpeters/Product-Manager-Skills★ 8ksame name
- indranilbanerjee/digital-marketing-pro★ 934same name
- duncan-buildroom/freeskills★ 65same name
- duncan-buildroom/profit-room-skills★ 18same name
- calven-ai/marketing-as-code★ 10same name
- 2104178150-ai/megaphone★ 7same name
- styfinity/claude-marketing-department★ 6same name
- impactbrussels/FounderOS★ 2same name
- agentmart/pm-os★ 1same name
- agentdynarq/founder-skills★ 0same name
4 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 repository19 other files it gives its agents.
- customer-discovery-jtbd-synthesisSkill
- event-tracking-planSkill
- experiment-design-readoutSkill
- launch-planSkill
- north-star-metricSkill
- onboarding-activation-auditSkill
- positioning-messagingSkill
- pricing-packaging-hypothesisSkill
- retention-diagnosisSkill
- seo-geo-content-briefSkill
- customer-discovery-jtbd-synthesisSkill
- event-tracking-planSkill
- experiment-design-readoutSkill
- north-star-metricSkill
- onboarding-activation-auditSkill
- positioning-messagingSkill
- pricing-packaging-hypothesisSkill
- retention-diagnosisSkill
- seo-geo-content-briefSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
6
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 9
Use this skill when the user wants a structured plan for launching a new feature, product, campaign, or GTM motion.
- Distinctive: line 38
If some are missing, infer and label assumptions.
- Distinctive: line 43
Ensure product, marketing, sales, success, and analytics are aligned where relevant.
- Distinctive: line 45
Do not treat launch as only a publishing event.
- Distinctive: line 143
If the launch is for a PLG feature:
- Distinctive: line 148
If the launch is enterprise-facing:
“Common” is measured: kept by at least 6 in 10 of the 11 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 Plan
Use this skill when the user wants a structured plan for launching a new feature, product, campaign, or GTM motion.
What this skill must produce
Always produce:
- Launch summary
- Audience / segmentation
- Core message
- Asset checklist
- Launch timeline
- Measurement plan
- Risk register
- Post-launch review plan
Inputs to gather
If possible, extract:
- what is launching
- who it is for
- problem solved
- launch type (beta / GA / pricing / category / lifecycle / campaign)
- business goal
- launch date
- stakeholders
- dependencies
- channels
- available proof / assets
If some are missing, infer and label assumptions.
Working rules
- Tie launch activity to a clear customer problem and target audience.
- Ensure product, marketing, sales, success, and analytics are aligned where relevant.
- Include both pre-launch readiness and post-launch measurement.
- Do not treat launch as only a publishing event; include enablement and feedback loops.
Step-by-step method
Step 1: define the launch
State:
- what is launching
- for whom
- why now
- what should happen if launch succeeds
Step 2: define audience slices
Segment:
- who should hear about it first
- who should not
- who needs a tailored version of the message
Step 3: define core narrative
Write:
- one-sentence positioning for the launch
- key benefits
- proof
- objections
Step 4: identify channels and assets
List what is needed for:
- homepage / landing page
- product UI
- lifecycle email
- social
- sales enablement
- support / success enablement
- docs / help center
- changelog / release notes
Step 5: define timeline
Split into:
- pre-launch
- launch day
- post-launch week 1-2
- post-launch month 1
Step 6: define metrics
Include:
- awareness metrics
- adoption metrics
- activation / usage metrics
- revenue / pipeline metrics if relevant
- qualitative feedback
Step 7: define review cadence
Plan post-launch reviews and decisions.
Output structure
Launch summary
- Launch:
- Type:
- Audience:
- Goal:
- Success looks like:
Audience / segmentation
| Segment | Why they care | Message angle | Channel |
Core message
- One-liner:
- Headline:
- 3 key benefits:
- Proof points:
- Main objection and response:
Asset checklist
| Asset | Owner | Needed by | Status |
Launch timeline
| When | Action | Owner | Dependency |
Measurement plan
| Metric | Why it matters | Owner | Review cadence |
Risk register
| Risk | Likelihood | Impact | Mitigation |
Post-launch review plan
- 24h review:
- 7-day review:
- 30-day review:
- launch questions to answer:
- go / iterate / rollback criteria:
Special instructions
If the launch is for a PLG feature:
- include in-product announcement and lifecycle messaging
- define product-qualified behavior
- include self-serve conversion and team expansion signals
If the launch is enterprise-facing:
- include sales enablement, objection handling, and customer-success briefing
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.

