product-launch
Skill53 starsChanged 5 days agoMITView on GitHub
Plans a product launch from a brief: launch tier, 5-8 launch tactics, narrative angle, objectives, then the assets and a T-14 to T+30 timeline built from those tactics. Use when asked to plan a launch, a launch strategy or a go-to-market for a feature.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- luongnv89/skillstheir own version, first seen Nov 8, 2026
- alunadev/ald-skillstheir own version, first seen Nov 8, 2026
- astDeniss/business-skillstheir own version, first seen Nov 1, 2026
- genspark-ai/genofficetheir own version, first seen Oct 25, 2026
- NinjaSln-labs/agent-skillstheir own version, first seen Oct 2, 2026
- risukisu/marketing-skillstheir own version, first seen Sep 28, 2026
Used with
Projects with it also use business-plan, email-marketing and 6 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
LangChainSkillcompetitor-analysis
Analyze competitors in a given market segment. Trigger on: competitive landscape, competitor analysis, market comparison, competitive positioning.
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
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- genspark-ai/genoffice★ 12ksame name
- vivy-yi/xiaohongshu-skills★ 455same name
- luongnv89/skills★ 145same name
- chuhaiqu/skills★ 22same name
- astDeniss/business-skills★ 8same name
- risukisu/marketing-skills★ 6same name
- alunadev/ald-skills★ 4same name
- kevinaimonster/skill-hub★ 4same name
- arielnishri-svg/claude-skills★ 1same name
- buildingwithai/skills★ 1same name
6 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 repository9 other files it gives its agents.
- aeo-strategySkill
- battlecardsSkill
- case-studySkill
- company-contextSkill
- competitor-researchSkill
- icp-researchSkill
- linkedin-profileSkill
- positioningSkill
- tov-guidelinesSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
4
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 52
Before proceeding, verify the feature brief includes name, category, description, target personas, key capabilities.
- Distinctive: line 54
If inputs are missing: ask the user for the brief, the messaging and the target personas, or draft them from the product page and confirm …
- Distinctive: line 107
If you've ever shipped something that got crickets, this skill fixes it.
- Very specific: line 111
Every launch happens in a cultural context.
- Very specific: line 146
No invented metrics: Use provided proof points or mark as [PLACEHOLDER: metric].
- Very specific: line 148
Mark placeholders clearly: Use [PLACEHOLDER: description] for unconfirmed details.
- Distinctive: line 167
Use product-messaging output directly
“Common” is measured: kept by at least 6 in 10 of the 12 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
Architect and execute B2B SaaS product launches that drive sustained pipeline. Launches are built on the tactics around the event — not the channel checklist. Pick 5–8 tactics from the 16-tactic library; derive assets from the chosen tactics; orchestrate across pre-launch, launch day, and post-launch.
Claude Code triggers
Invoke when user says:
- "Product launch for [feature/product]"
- "Feature launch plan"
- "Launch strategy for [company]"
- "GTM launch plan"
- "New feature announcement"
- "Create launch assets"
- "Launch timeline for [feature]"
- "Launch checklist"
- "Plan a launch for [feature]"
- "Launch playbook"
Do NOT invoke when the user wants only landing page copy, product messaging, LinkedIn content, email copy, or live event production.
Input requirements
Required
| Input | Description | Source |
| Product feature brief | What's launching, target release date | User provides |
| Product messaging | Capabilities, benefits, differentiators | User provides or existing doc |
| ICP research | Target personas, pain points, proof points | User provides or existing doc |
Optional (improve quality)
| Input | How it helps |
| TOV guidelines | Brand voice for all copy assets |
| Competitor launches | Differentiation framing |
| Sales objections | FAQ and enablement content |
| Customer feedback | Proof points and testimonials |
| Launch date | Timeline anchoring |
Validation
Before proceeding, verify the feature brief includes name, category, description, target personas, key capabilities; product messaging available or generated; ICP research available or generated; launch date confirmed (or flexible window).
If inputs are missing: ask the user for the brief, the messaging and the target personas, or draft them from the product page and confirm before going further.
Core frameworks
Launch philosophy
The old launch playbook is dead. Most marketers launch by writing "we're excited to announce" on LinkedIn, ticking off a channel checklist (Product Hunt / Hacker News / Reddit / LinkedIn / X), and wondering why their CEO asks "wait, did we even launch?" the following Monday.
A great launch is built on the tactics around the launch — not the channel checklist. The skill encodes 16 tactics in the premium reference. Strategy phase picks 5–8 of them. Development phase derives assets from the chosen tactics, not from a default 18-asset list.
The order matters: tactics first, then assets. Reverse this and you're back to the channel checklist mentality.
A launch built this way:
- Pre-builds audience before launch day (waitlist, teaser, ambassador, partner)
- Stages a real moment (live event, drop, named version)
- Sustains attention for 2+ weeks post-launch (recap cadence)
- Compounds across cycles (60-day relaunch every quarter)
T-0 is the midpoint, not the destination. And the channel checklist is not the strategy.
Three-phase architecture
| Phase | Purpose | Duration | Deliverables |
| Strategy | Pick 5–8 tactics; define narrative, objectives, positioning | T-14 to T-10 | Strategy brief with selected tactics, narrative angle, success metrics |
| Development | Produce assets derived from chosen tactics | T-10 to T-1 | Asset list scoped to tactics (not a default 18-asset checklist) |
| Deployment | Orchestrate timeline and amplification | T-14 to T+14 | Timeline, coordination playbook |
Launch tiers
| Tier | Description | Tactic count | Asset scope |
| Major | New product, category entry, platform shift | 7–8 tactics | Live event + waitlist + teaser + ambassadors + partner + recap + relaunch + paid |
| Significant | Major feature, integration, pricing change | 5–7 tactics | Subset above; selective paid |
| Standard | Feature improvement, capability expansion | 4–6 tactics | Channel-specific copy + recap + founder personal posts + 1–2 others |
| Minor | Bug fix, UX improvement | 3–4 tactics | Channel-specific copy + recap + grandfather (if applicable) |
Anything counts as a launch
The 16-tactic library doesn't only apply to product launches. The same machinery runs for:
- Stealth exits — coming out of stealth is a launch
- Feature drops — significant feature releases
- Hiring announcements — exec hires, team scale-ups
- Pricing changes — new tiers, plan refactors (always pair with grandfather policy)
- Big blog posts — flagship content, research releases
- Funding announcements — Series A/B/C, secondary rounds
- Partnership reveals — when a partner co-launch IS the launch
- Geographic expansion — entering a new market
If you've ever shipped something that got crickets, this skill fixes it. The trigger isn't "is this a product?" — it's "are we asking the audience to pay attention?" If yes, run the playbook.
Seasonal alignment
Every launch happens in a cultural context. Check for adjacent cultural moments (±14 days from launch), score alignment fit (Strong/Medium/Weak/Negative), choose strategy (ride the wave, counter-program, ignore, or avoid), and adapt messaging (hooks, imagery, CTAs). See the premium reference.
Tactic library — Strategy starts here
Before anything else in the Strategy phase, pick 5–8 tactics from the premium reference. The 16-tactic menu covers waitlist, ambassador army, partner co-launch, channel-specific copy, founder personal posts, gamified drops, filtered giveaways, weird swag, audience-as-detective narratives, named versions, public roadmap voting, grandfather policy, teaser videos, live events, recap cadences, and 60-day relaunches.
Selection criteria: launch tier, audience size, ICP shape, resource constraints, existing community signal. The chosen tactics drive the Development phase asset list — not a default 18-asset checklist.
Three battle-tested stacks live in the premium reference as starting points:
- Clicky stack — Waitlist → Teaser → Live event → Recap. Best for momentum into a live event.
- Long-tail stack — Ambassador army → Partner co-launch → 60-day relaunch. Best for cold audiences and limited founder time.
- Drama stack — Narrative campaign → Named version → Recap. Best for personality-led brands.
Most launches won't match a stack cleanly — combine across stacks. The 5–8 selection rule is the discipline.
Process
The launch runs in three phases. Read the premium reference for the full step-by-step (5 strategy steps, 8 development steps, 4 deployment steps, plus per-phase checkpoints and the process flowchart).
Phase summary:
- Strategy (T-14 to T-10) — feature brief, 5–8 tactics selected from the tactic menu, narrative angle, business objectives, kick-off agenda
- Development (T-10 to T-1) — derive assets from chosen tactics (not from a default 18-asset checklist), produce each via its template-spec
- Deployment (T-14 to T+14) — pre-launch / launch-day / post-launch timelines + coordination playbook with RACI
Anti-hallucination guardrails
- Ground all claims in inputs. Feature benefits must come from product brief or messaging.
- No invented metrics. Use provided proof points or mark as
[PLACEHOLDER: metric]. - Quote verbatim. Customer quotes from ICP research only.
- Mark placeholders clearly. Use
[PLACEHOLDER: description]for unconfirmed details. - Cite sources. Link each asset to its input source.
MCP data integration
Level: 2 — PM Execution (inherits strategy, operational pulls)
Inherits from: product-messaging
Pulls fresh
| Source | What to pull | Tool | When |
| Slack | Launch coordination threads | slack_search_public | Always |
Fallback (no MCP)
- Use product-messaging output directly
- Manual launch coordination via shared docs
- User-provided timeline and stakeholder info
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.

