Plan and execute technical product launches for developer tools, APIs, and technical products. Use this skill when technical PMMs need to "plan a launch", "create a launch strategy", "coordinate a product release", or "prepare for GA/beta launch".
Plans and executes technical product launches for developer tools, APIs, and SDKs. Use when you need to coordinate a release, create launch strategy, or prepare for GA/beta launches.
/plugin marketplace add jamesrochabrun/skills/plugin install all-skills@skills-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/developer_enablement.mdreferences/launch_messaging.mdreferences/launch_tiers.mdreferences/metrics_frameworks.mdscripts/assess_launch_tier.shscripts/generate_launch_plan.shscripts/validate_readiness.shPlan and execute successful launches for technical products, developer tools, APIs, SDKs, and platforms. This skill provides frameworks, checklists, and templates specifically designed for technical audiences and developer-focused products.
Built for:
Run the interactive assessment:
scripts/assess_launch_tier.sh
This determines if your launch is:
Create your comprehensive launch plan:
scripts/generate_launch_plan.sh
Provides structured plan with:
Before launch, check readiness:
scripts/validate_readiness.sh
Validates:
Different launches require different levels of investment:
| Tier | Type | Examples | Investment |
|---|---|---|---|
| Tier 1 | Major | GA launch, new product, major version | Full GTM, events, PR |
| Tier 2 | Standard | New features, integrations, SDKs | Selective GTM, blog, docs |
| Tier 3 | Minor | Updates, improvements, patches | Changelog, in-app |
See references/launch_tiers.md for complete framework.
Critical for technical launches:
Documentation:
Code Assets:
Developer Experience:
See references/developer_enablement.md for complete checklist.
Speak developer language:
Avoid:
Include:
See references/launch_messaging.md for templates.
Where developers discover new tools:
Primary:
Secondary:
Tertiary:
Objectives:
Activities:
Launch Tier Assessment
scripts/assess_launch_tier.sh
Stakeholder Kickoff
Define Success Metrics
Create Launch Timeline
scripts/generate_launch_plan.sh
Objectives:
Activities:
Documentation:
Code Assets:
Marketing Assets:
Sales Enablement:
Objectives:
Activities:
Internal Enablement:
External Prep:
Technical Validation:
scripts/validate_readiness.sh
Pre-Launch Checklist:
Launch Day Playbook:
Morning (9 AM):
Midday (12 PM):
Afternoon (3 PM):
End of Day:
Objectives:
Activities:
Week 1:
Week 2:
Week 4:
When:
Timeline: 12-16 weeks
Investment:
Deliverables:
When:
Timeline: 6-8 weeks
Investment:
Deliverables:
When:
Timeline: 2-4 weeks
Investment:
Deliverables:
Launch is NOT ready without:
Developer rule: "If it's not documented, it doesn't exist"
Developers want to see code:
Good:
# Initialize the SDK
import acme_sdk
client = acme_sdk.Client(api_key="your_key")
result = client.widgets.create(name="My Widget")
print(result.id)
Bad: "Our SDK makes it easy to create widgets with just a few lines of code"
Engagement hierarchy:
Developers appreciate:
Developers hate:
Engage where developers are:
Don't:
Activation:
Engagement:
Retention:
See references/metrics_frameworks.md for complete guide.
# Introducing [Feature/Product]
## The Problem
[Describe the developer pain point in technical detail]
## The Solution
[High-level technical overview]
## How It Works
[Technical architecture, with diagram]
## Getting Started
[Code sample showing basic usage]
## What's Next
[Roadmap tease]
[Link to full documentation]
Subject: [Feature] is now available
Body:
Hi [Developer Name],
We're excited to announce [Feature] is now generally available.
What it does:
[One sentence technical description]
Why it matters:
[Developer benefit]
Get started in 5 minutes:
[Code snippet or quick start link]
Key resources:
- Documentation: [link]
- Sample code: [link]
- API reference: [link]
Questions? Reply to this email or join us in [Discord/Slack].
Happy building!
[Your Name]
## [Version] - YYYY-MM-DD
### Added
- [New feature]: [Technical description]
- Example: `client.newMethod(params)`
- [Link to docs]
### Changed
- [Breaking change]: [What changed and why]
- Migration guide: [link]
### Fixed
- [Bug fix]: [What was fixed]
### Deprecated
- [Feature]: [Timeline for removal]
Coordination needed:
Partner Enablement:
Launch Activities:
Metrics Review:
What Worked:
What Didn't:
Action Items:
Template: [Document in Notion/Confluence]
Problem: "Docs will be ready soon" = Dead launch
Solution: Docs are non-negotiable. Delay launch if needed.
Problem: "Revolutionary", "Seamless", "Game-changing"
Solution: Use concrete technical language, metrics, code.
Problem: Breaking changes with no migration guide
Solution: Clear migration guide, migration tools, version support plan.
Problem: All effort on Day 1, nothing for ongoing adoption
Solution: Plan 4-week post-launch content calendar.
Problem: Launch and disappear
Solution: Active community engagement, regular office hours.
Product: New REST API for developer platform
Timeline: 12 weeks
Key Activities:
Results:
Product: Integration with popular DevOps tool
Timeline: 6 weeks
Key Activities:
Results:
Product: New SDK version with performance improvements
Timeline: 2 weeks
Key Activities:
Results:
Technical launches require:
Use the scripts to streamline planning, follow the frameworks for consistency, and always put developers first.
Get started:
scripts/assess_launch_tier.sh
Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.