From solo
Generates go-to-market launch strategies from PRD, research, and project docs. Validates beachhead segments, pricing against manifesto principles, maps channels, and outputs actionable checklists.
npx claudepluginhub fortunto2/solo-factory --plugin soloThis skill is limited to using the following tools:
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.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
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."
kb_search(query) — find launch methodology, past launchesweb_search(query) — research channels, communities, pricing benchmarksproject_info(name) — get project stack and statusIf MCP tools are not available, fall back to Glob + Grep + WebSearch.
Parse project from $ARGUMENTS.
docs/prd.md — features, ICP, pricing, acceptance criteriadocs/research.md — competitors, personas, market size, pain pointsCLAUDE.md — stack, deploy targetValidate beachhead segment:
Check if PRD has a beachhead section (added by /validate). If not, define it now:
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-outreach |
| Reddit (specific subs) | Low | Free | Week 1 | 50-100 visits, pain validation | /community-outreach |
| SEO / Content | Medium | Free | Month 1-3 | Organic traffic baseline | /seo-audit + /landing-gen |
| Twitter/LinkedIn | Low | Free | Ongoing | Network effect, credibility | /content-gen |
| Paid (if justified) | High | $50-200 | After organic validates | Scale what works | — |
Rules:
Launch timeline (4-week plan):
Week 0 (pre-launch):
- [ ] /landing-gen — landing page with email capture
- [ ] /seo-audit — baseline SEO score
- [ ] /metrics-track — PostHog events wired
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 feedback
Adapt 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:
Launch risks (from research.md + pre-mortem thinking):
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:
Cause: Haven't run /validate yet.
Fix: Run /validate <idea> first to generate PRD with ICP, pricing, and features.
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.
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.