product-launch
Skill1 starsChanged 12 months agoMITView on GitHub
Execute product launches using 90-day roadmaps, launch tier frameworks, and post-launch optimization. For B2B/SaaS, consumer products, and feature releases. Includes solopreneur and enterprise coordination strategies.
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use this skill when you need to:
- Distinctive: line 47
When to use each tier
- Distinctive: line 141
Not all launches deserve equal resources:
- Very specific: line 218
Check: Do you have positioning/messaging?
- Distinctive: line 221
Follow your tier's playbook
- Distinctive: line 226
Use checklists to verify nothing missed
- Very specific: line 235
Read core/01-launch-tier-framework.md to determine tier
- Very specific: line 239
Use positioning skill (1-2 weeks)
“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
Product Launch
Execute product launches from planning through post-launch optimization.
📊 RESEARCH-BACKED: Built from 2024-2025 research across Product Marketing Alliance and launch frameworks.
When to Use This Skill
Use this skill when you need to:
- Plan product launches - 90-day roadmaps, launch tiers, resource allocation
- Execute launches - Day-of coordination, multi-channel tactics
- Coordinate teams - Cross-functional RACI, stakeholder management
- Optimize post-launch - Metrics, iteration, growth tactics
NOT for:
- Positioning (use
positioningskill - PREREQUISITE) - Messaging (use
messagingskill - PREREQUISITE) - Message testing (use
rollout-and-launchskill) - Deep sales enablement (use
sales-enablementskill)
Prerequisites: Clear positioning and validated messaging required before launching.
The Launch Process
Timeline: 16-24 weeks (Tier 1), 8-12 weeks (Tier 2), 1-4 weeks (Tier 3)
PLAN → BUILD → PREPARE → LAUNCH → OPTIMIZE
(4-6w) (4-8w) (2-4w) (1 day) (4-8w continuous)How to Navigate This Skill
Core Process (8 files)
PHASE 1: PLANNING
references/core/01-launch-tier-framework.md⭐ START HERE- Tier 1/2/3 framework
- Resource allocation
- When to use each tier
references/core/02-90-day-roadmap.md- Phase-by-phase timeline
- Milestone tracking
- Compressed vs full timelines
references/core/03-gtm-strategy.md- Product-led vs sales-led
- Channel strategy
- Budget allocation (60-30-10)
PHASE 2: EXECUTION
references/core/04-cross-functional-coordination.md- RACI matrix for launches
- Solopreneur vs enterprise playbooks
- Stakeholder management
references/core/05-multi-channel-tactics.md- Community tactics (Product Hunt, Reddit, LinkedIn)
- Content marketing
- SEO and paid strategies
references/core/06-launch-day-playbook.md- Hour-by-hour execution
- War room setup
- Crisis protocols
PHASE 3: POST-LAUNCH
references/core/07-metrics-optimization.md- AARRR Pirate Metrics
- KPIs by launch tier
- Dashboard setup
references/core/08-iteration-retrospective.md- Feedback loops
- Rapid iteration cycles
- Launch retrospectives
Advanced Topics (5 files)
references/advanced/product-hunt-mastery.md- Deep PH tacticsreferences/advanced/pricing-packaging.md- Value-based pricing for launchesreferences/advanced/beta-testing-programs.md- Beta program designreferences/advanced/failed-launch-recovery.md- Recovery strategiesreferences/advanced/international-expansion.md- Market-specific launches
Templates & Checklists
assets/templates/90-day-roadmap.md- Planning timelineassets/templates/launch-tier-assessment.md- Tier determinationassets/templates/raci-matrix.md- Responsibility mappingassets/checklists/launch-day-checklist.md- Hour-by-hour executionassets/checklists/pre-launch-checklist.md- Pre-launch validation
Total: 13 files (8 core + 5 advanced) - Moderate complexity
Quick Decision Trees
What tier is my launch? → New product or market = Tier 1 → Major feature, revenue impact = Tier 2 → Minor update = Tier 3 → Read: core/01-launch-tier-framework.md
I'm a solopreneur: → Read: core/01-launch-tier-framework.md (solopreneur section) → Then: core/04-cross-functional-coordination.md (solo playbook) → Focus on: core/05-multi-channel-tactics.md (community tactics)
I'm in an enterprise: → Read: core/01-launch-tier-framework.md → Then: core/04-cross-functional-coordination.md (enterprise section) → Focus on: RACI, stakeholder management
I don't have positioning/messaging:
→ STOP - Use positioning skill first (1-2 weeks)
→ Then use messaging skill (2-3 weeks)
→ Return here when complete
Key Principles
1. Positioning and Messaging Are Prerequisites
Cannot launch without:
- Clear positioning (who you're for, why different)
- Validated messaging (value props that resonate)
95% of products fail due to insufficient market understanding.
2. Launch Tiers Prevent Burnout
Not all launches deserve equal resources:
- Tier 1: Max 2 per quarter, full resources
- Tier 2: 4-8 per quarter, selective resources
- Tier 3: Ongoing, minimal resources
3. First 48 Hours Matter Most
Launch day requires:
- War room intensity
- Hour-by-hour playbook
- Real-time monitoring
- Crisis protocols
4. Post-Launch is Where Work Begins
Week 1 feedback reveals what planning missed:
- 2-week sprint cycles
- Tight feedback loops
- AARRR metrics
Related Skills
Prerequisites (complete FIRST):
positioning- Who you're for, differentiation (1-2 weeks)messaging- Value propositions, multi-audience (2-3 weeks)
Complementary:
sales-enablement- Deep battlecards, trainingcompetitive-intelligence- Market analysisrollout-and-launch- Message testing, workshops
For specific launch types:
personas- Buyer intelligencepricing-packaging- Advanced pricing (if not using core/advanced here)
Integration Workflow
Step 1: POSITIONING (positioning skill) → 1-2 weeks
Step 2: MESSAGING (messaging skill) → 2-3 weeks
Step 3: LAUNCH PLANNING (this skill, core 1-3) → 4-8 weeks
Step 4: LAUNCH EXECUTION (this skill, core 4-6) → 2-4 weeks + 1 day
Step 5: POST-LAUNCH (this skill, core 7-8) → 4-8 weeksSuccess Metrics by Tier
Tier 1 - Week 1 Targets
| Metric | Good | Great | Exceptional |
| Sign-ups | 500+ | 1,000+ | 2,500+ |
| Activation | 25% | 40% | 60% |
| Product Hunt | 200+ | 500+ | 1,000+ |
| MRR (B2B) | $5K | $10K | $25K+ |
Full metrics in core/07-metrics-optimization.md
Typical Timelines
| Launch Tier | Timeline | Minimum |
| Tier 1 (Major) | 16-24 weeks | 12-16 weeks |
| Tier 2 (Feature) | 8-12 weeks | 6-8 weeks |
| Tier 3 (Update) | 1-4 weeks | N/A |
Common Pitfalls
- Skipping positioning/messaging → 95% failure rate
- No tier framework → Team burnout
- Weak pre-launch testing → Launch day bugs
- No post-launch plan → Momentum dies
- Missing cross-functional alignment → Conflicting stories
Getting Started
New to launches?
- Check: Do you have positioning/messaging? (If NO, use those skills first)
- Read: core/01-launch-tier-framework.md
- Read: core/02-90-day-roadmap.md
- Follow your tier's playbook
Have experience?
- Confirm tier: core/01-launch-tier-framework.md
- Jump to your phase (planning/execution/post-launch)
- Use checklists to verify nothing missed
Mid-launch? → Jump to core/06-launch-day-playbook.md → Use assets/checklists/launch-day-checklist.md
Ready to start?
- Read core/01-launch-tier-framework.md to determine tier
- Then core/02-90-day-roadmap.md to plan timeline
Need positioning first?
- Use
positioningskill (1-2 weeks) - Then
messagingskill (2-3 weeks) - Return here when ready
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- genspark-ai/genoffice★ 11ksame name
- vivy-yi/xiaohongshu-skills★ 455same name
- chuhaiqu/skills★ 22same name
- astDeniss/business-skills★ 8same name
- risukisu/marketing-skills★ 6same name
- kevinaimonster/skill-hub★ 4same name
- arielnishri-svg/claude-skills★ 1same name
- NinjaSln-labs/agent-skills★ 1same name
- sawzhang/skills_demo★ 1same name
- Typeless-Git/skills★ 1same name
3 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.
Used alongsideProjects with it also use business-plan, email-marketing and 4 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.
walternateSkillbusiness-plan
Write, structure, and update a business plan for a solopreneur. Use when creating a plan from scratch, updating an existing plan after a pivot or new phase, or preparing a plan to share with investors, partners, or even just to clarify your own strategy. Covers executive summary, market analysis, competitive positioning, revenue model, operations plan, financial projections, and risk assessment — all adapted for a one-person business. Trigger on "write a business plan", "business plan", "create my plan", "business plan template", "update my business plan", "plan for my business", "investor pitch plan".
Also in 3 projects that use this
claude-office-skillsSkillemail-marketing
Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics
Also in 3 projects that use this
silvainfmSkillpricing-strategy
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' or 'monetization.' This skill covers pricing research, tier structure, and packaging strategy.
Also in 3 projects that use this
AnthropicSkillcontent-strategy
Analyzes sales data from PayPal and QuickBooks to find top performers and slow movers, layers in seasonality, and produces a prioritized 30-day content brief: what to push, what offers to run, what to hold. Strategic output only — no calendars or assets. Use when the user asks what to post, wants a content plan, asks what's selling, or what to promote this month.
Also in 3 projects that use this
birne-skSkillmarket-research
Professional market research and competitive analysis using McKinsey/BCG/Bain consulting methodologies. Use when analyzing markets, competitive landscapes, customer insights, or strategic positioning. Generates hypothesis-driven research with PPTX presentation deliverables.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
In this repository15 other files it gives its agents.
- music-video-directionSkill
- office-comedy-skillSkill
- viral-validation-labSkill
- competitive-intelligenceSkill
- messaging-rolloutSkill
- messagingSkill
- personasSkill
- pierri-website-messagingSkill
- positioning-rolloutSkill
- positioningSkill
- pricing-packagingSkill
- rollout-and-launchSkill
- sales-enablementSkill
- strategic-thinkingSkill
- world-class-prioritizationSkill
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.

