Skip to content

heyparsadev/claude-venture-plugin / venture/skills/gtm

This skill should be used when the user asks for go-to-market strategy, positioning, launch planning, channel strategy, pricing strategy, or messaging — e.g. "build a GTM strategy", "how should we launch", "which channels should we use", "positioning for my product", "pricing strategy", "استراتژی ورود به بازار", "گوتومارکت", "پلن لانچ", "از چه کانالی مشتری بیاریم", "قیمت‌گذاری", "پوزیشنینگ". Produces a positioning canvas, messaging house, channel plan, pricing strategy, and launch plan in the venture workspace.

references/launch-checklist.md

View on GitHub
# Launch Plan Template

Calibrate to reality: "launch" for a B2B niche tool = 20 warm emails + 3 community posts. For consumer = coordinated spike. Both are launches; size the checklist accordingly, assign an owner and date to every item.

```markdown
# Launch Plan — <Venture>
<date> · launch type: <soft beta | public launch | new-market entry> · target date: <date>

## Goals (pick 1 primary)
- Primary: <e.g. 100 signups week 1 | 10 demo calls | 30 beta users giving feedback>
- Secondary: <email list, social follows, press mention>

## Pre-launch (T−4 to T−1 weeks)
- [ ] Positioning & messaging finalized (from messaging house) — <owner/date>
- [ ] Landing page live with analytics + signup path tested end-to-end
- [ ] Beta/waitlist warm-up: <how many contacts, where from>
- [ ] Assets: demo video/screenshots, launch post drafts per channel, FAQ
- [ ] Onboarding ready for strangers (someone outside the team completed it unaided)
- [ ] Support path: who answers, where (email/Telegram/chat), response SLA
- [ ] Pricing & payment tested (real transaction + refund)

## Launch window (day-by-day)
| Day | Action | Channel | Owner |
|---|---|---|---|
| D0 | <announce to warmest audience first> | | |
| D1 | <community/platform posts> | | |
| D2–6 | <follow-ups, engage every comment/reply, daily metric check> | | |

## Post-launch (the part that matters)
- [ ] Week 2: personally contact first ~20 users — what almost stopped them?
- [ ] Week 2–4: double down on the one channel that produced signal; kill the silent ones
- [ ] Week 4: activation/retention snapshot → feeds `/venture:pmf`
- [ ] Week 4: retro — what to repeat next launch

## Risk prep
- <top 2 launch risks (e.g. onboarding breaks under load, crickets) + mitigation for each>
- Crickets plan: if <metric> < <floor> by D3 → <pre-decided response: revise hook, second wave, direct outreach>
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall