hoavdc/CodexKit / skills/codexkit-go-to-market-planner
codexkit-go-to-market-planner
VerifiedBuild a Go-to-Market (GTM) plan for new product launches, market entries, or feature rollouts. Covers market sizing (TAM/SAM/SOM), positioning, messaging, channel strategy, pricing approach, and launch timeline. Use when preparing to bring something new to market. Do not use for ongoing marketing operations or campaign execution.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.5 KB |
| agents/openai.yaml | config | 168 B |
| examples/common-mistakes.md | markdown | 787 B |
| examples/good-output.md | markdown | 865 B |
| verification/checklist.md | markdown | 1.4 KB |
examples/common-mistakes.md
View on GitHub# Common Mistakes — Go-to-Market Planner
> Anti-patterns to watch for when using the Go-to-Market Planner skill.
## 1. Target everyone
**What goes wrong:** 'Any company that needs compliance' — too broad to execute
**How to fix it:** Define ICP with firmographic + behavioral criteria. 'If you can't name 50 prospects, it's too broad.'
## 2. All channels, no priority
**What goes wrong:** Listing 8 marketing channels without ranking or budgeting
**How to fix it:** Pick 2 primary channels. Fund and measure for 90 days before adding more.
## 3. Pricing by cost-plus, not value
**What goes wrong:** Setting price based on development cost, not customer willingness to pay
**How to fix it:** Price based on value delivered vs alternatives. Run pricing sensitivity research.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |