solo-launch
Skill18 starsChanged 4 months agoMITView on GitHub
Use when "launch plan", "go-to-market", "GTM strategy", "how to launch", "launch checklist", "growth plan", or product is built and needs distribution strategy. Do NOT use for content generation (/content-gen) or SEO audit (/seo-audit).
In this repository62 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- solo-android-releaseSkill
- solo-apple-app-iconSkill
- solo-auditSkill
- solo-boardSkill
- solo-buildSkill
- solo-community-outreachSkill
- solo-content-genSkill
- solo-creator-growthSkill
- solo-customer-finderSkill
- solo-deep-researchSkill
- solo-deploySkill
- solo-diagnoseSkill
- solo-domainSkill
- solo-factorySkill
- solo-github-outreachSkill
- solo-gmail-cliSkill
- solo-grillSkill
- solo-hackathonSkill
- solo-humanizeSkill
- solo-i18nSkill
- solo-index-youtubeSkill
- solo-initSkill
- solo-ios-devSkill
- solo-ios-releaseSkill
- solo-kaggle-gpuSkill
- solo-kindleSkill
- solo-knowledgeSkill
- solo-landing-genSkill
- solo-legalSkill
- solo-memory-auditSkill
- solo-metrics-trackSkill
- solo-mirrorSkill
- solo-model-shrinkSkill
- solo-music-reels-cutSkill
- solo-open-datasetSkill
- solo-paperSkill
- solo-pdf-printSkill
- solo-pipelineSkill
- solo-planSkill
- solo-redditSkill
- solo-researchSkill
- solo-retroSkill
- solo-reviewSkill
- solo-scaffoldSkill
- solo-secretsSkill
- solo-seo-auditSkill
- solo-seo-cliSkill
- solo-setupSkill
- solo-sgrSkill
- solo-skill-auditSkill
- solo-skill-shelfSkill
- solo-stem-splitSkill
- solo-streamSkill
- solo-supervoxSkill
- solo-swiftui-design-systemSkill
- solo-transcribeSkill
- solo-validateSkill
- solo-video-editSkill
- solo-video-promoSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 6 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
If MCP tools are not available, fall back to Glob + Grep + WebSearch.
- Very specific: line 31
Read docs/prd.md — features, ICP, pricing, acceptance criteria
- Very specific: line 32
Read docs/research.md — competitors, personas, market size, pain points
- Distinctive: line 33
Read CLAUDE.md — stack, deploy target
- Distinctive: line 34
If none found: ask via AskUserQuestion
- Very specific: line 38
Check if PRD has a beachhead section (added by /validate).
- Very specific: line 47
Read pricing from PRD. Check against principles in templates/principles/manifest.md:
- Distinctive: line 57
If pricing conflicts with principles, flag it and suggest alternatives.
- Distinctive: line 72
Start with free channels — paid only after organic validates demand
- Distinctive: line 123
Channel risk: if primary channel fails, what's the backup?
- Very specific: line 189
Fix: Run /validate <idea> first to generate PRD with ICP, pricing, and features.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
/launch
Generate a go-to-market launch strategy that ties together all promotion skills into a unified plan. Reads PRD and research data, defines the beachhead, maps channels, validates pricing against manifesto principles, and produces an actionable launch checklist.
Philosophy: Launch is not a single event — it's a sequence of small bets. Each channel is an experiment. Measure before scaling. Reference: manifesto principle "Money without overheating — revenue before automation, scale what works."
MCP Tools (use if available)
kb_search(query)— find launch methodology, past launchesweb_search(query)— research channels, communities, pricing benchmarksproject_info(name)— get project stack and status
If MCP tools are not available, fall back to Glob + Grep + WebSearch.
Steps
- Parse project from
$ARGUMENTS.- Read
docs/prd.md— features, ICP, pricing, acceptance criteria - Read
docs/research.md— competitors, personas, market size, pain points - Read
CLAUDE.md— stack, deploy target - If none found: ask via AskUserQuestion
- Read
Validate beachhead segment:
Check if PRD has a beachhead section (added by
/validate). If not, define it now:- Segment: narrow, specific group (not "everyone who needs X")
- Size estimate: how many people in this segment?
- Reachability: where do they gather online? (specific subreddit, community, newsletter)
- Willingness to pay: evidence from research.md or competitor pricing
- Why first: why this segment before others?
Pricing validation against manifesto:
Read pricing from PRD. Check against principles in
templates/principles/manifest.md:Check Pass/Fail Notes Does it cost to run? (server, API, storage) — If no → should be free or one-time Subscription justified? — Only if ongoing costs exist Is pricing transparent? — No hidden fees, clear what you get Lock-in risk? — Can user export data? Own their content? Subscription fatigue check — Is there a one-time alternative? If pricing conflicts with principles, flag it and suggest alternatives.
Channel mapping (3-5 channels, ordered by effort):
For each channel, define:
Channel Effort Cost Timeline Expected Result Skill ProductHunt Medium Free Day 1 200-500 visits, feedback /community-outreachReddit (specific subs) Low Free Week 1 50-100 visits, pain validation /community-outreachSEO / Content Medium Free Month 1-3 Organic traffic baseline /seo-audit+/landing-genTwitter/LinkedIn Low Free Ongoing Network effect, credibility /content-genPaid (if justified) High $50-200 After organic validates Scale what works — Rules:
- Start with free channels — paid only after organic validates demand
- One channel at a time — don't spread thin (manifesto: "wip = 1")
- Measure each channel before adding the next
- Offline-first products: app store optimization (ASO) over web marketing
Launch timeline (4-week plan):
Week 0 (pre-launch): - [ ] /landing-gen — landing page with email capture - [ ] /seo-audit — baseline SEO score - [ ] /metrics-track — superduper-analytics events wired (`seo products` shows the counter reporting) Week 1 (soft launch): - [ ] /community-outreach — 3-5 value-first posts in target communities - [ ] /content-gen — LinkedIn post + Twitter thread - [ ] Collect feedback, fix critical issues Week 2 (public launch): - [ ] ProductHunt launch (if web/SaaS) - [ ] App Store submission (if iOS) - [ ] /video-promo — demo video for landing page - [ ] Monitor metrics daily Week 3-4 (iterate): - [ ] Review metrics — kill/iterate/scale decision - [ ] Double down on best-performing channel - [ ] /content-gen — release notes for updates - [ ] Second community push based on feedbackAdapt timeline to product type (iOS has App Store review delays, web can launch same day).
Growth loops (sustainable, not hacks):
Design 1-2 growth loops appropriate to the product:
Content loop: User creates → content is public/shareable → new users discover → they create Referral loop: User gets value → shares with peer → peer signs up → both benefit SEO loop: Solve problem → write about it → rank → new users find solution → they use product Tool loop: Free tool solves adjacent problem → captures intent → funnels to main product
Rules:
- Loop must be natural, not forced (no "share to unlock" dark patterns — manifesto: against exploitation)
- Loop must benefit the user, not just the product
- Offline-first products: growth through quality and word-of-mouth, not viral mechanics
Launch risks (from research.md + pre-mortem thinking):
- Timing risk: is a competitor about to launch? Big industry event?
- Pricing risk: will users pay at this price point? Evidence?
- Channel risk: if primary channel fails, what's the backup?
- Technical risk: can the product handle 10x traffic? (serverless = yes, VPS = plan)
Write launch strategy to
docs/launch-strategy.md:--- type: launch-strategy status: draft title: "Launch Strategy — {Project Name}" created: {YYYY-MM-DD} tags: [{project}, launch, gtm] --- # Launch Strategy: {Project Name} ## Beachhead Segment {from step 2} ## Pricing {from step 3, with manifest alignment} ## Channels {table from step 4} ## Timeline {4-week plan from step 5} ## Growth Loops {from step 6} ## Risks {from step 7} ## Launch Checklist - [ ] Landing page live (`/landing-gen`) - [ ] SEO baseline checked (`/seo-audit`) - [ ] Metrics wired (`/metrics-track`) - [ ] Content pack ready (`/content-gen`) - [ ] Community posts drafted (`/community-outreach`) - [ ] Demo video planned (`/video-promo`) - [ ] Privacy policy published (`/legal`) - [ ] Kill/iterate/scale thresholds defined --- *Generated by /launch. Review and adapt before executing.*- Output summary:
- Beachhead segment (one line)
- Recommended pricing model
- Top 3 channels with timeline
- Growth loop type
- Path to generated launch-strategy.md
- Suggested next step: run the skills from the checklist
Notes
- This skill is a strategic planner — it doesn't execute. Run the referenced skills to produce actual content
- Launch strategy should be revisited after Week 2 metrics review
- For products with no cloud component (offline-first), skip paid channels and focus on ASO + community
Common Issues
No PRD found
Cause: Haven't run /validate yet.
Fix: Run /validate <idea> first to generate PRD with ICP, pricing, and features.
Pricing conflicts with manifesto
Cause: Product uses subscription model but has no running costs. Fix: This is intentional — the skill flags it. Consider one-time purchase or freemium instead.
Beachhead too broad
Cause: "Everyone who uses X" is not a beachhead. Fix: Narrow to a specific community, profession, or behavior pattern. You should be able to find them in one place.
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.

