Skip to content

hoavdc/CodexKit / skills/codexkit-go-to-market-planner

codexkit-go-to-market-planner

Verified

Build 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.

FileKindSize
SKILL.mdskill md4.5 KB
agents/openai.yamlconfig168 B
examples/common-mistakes.mdmarkdown787 B
examples/good-output.mdmarkdown865 B
verification/checklist.mdmarkdown1.4 KB

verification/checklist.md

View on GitHub
# 4C Verification Checklist — Go-to-Market Planner

> Use this checklist after generating output. Answer each question honestly.

## Correctness — Is it right?

- [ ] Target segments are defined by observable criteria (industry, size, behavior), not assumptions
- [ ] Channel strategy matches where the target audience actually researches and buys
- [ ] Pricing is benchmarked against at least 3 market comparables

## Completeness — Is it done?

- [ ] All GTM pillars covered: positioning, pricing, channels, launch timeline, success metrics
- [ ] Competitive positioning map includes at least the top 3 alternatives
- [ ] First 90 days plan is week-by-week, not just 'launch and see'

## Context-fit — Does it match?

- [ ] GTM approach matches company stage (startup scrappy vs enterprise polished)
- [ ] Resource requirements are realistic for the team size
- [ ] Launch timing accounts for market seasonality and competitive moves

## Consequence — Is it safe to use?

- [ ] If launch fails to hit 30-day targets, is there a pivot plan?
- [ ] If a competitor launches a similar feature next week, which elements of the plan are defensible?
- [ ] If sales team reads this plan, can they start selling from it?

---

**Final question:** _If this output were used immediately in production, what is the single biggest risk?_

Write the answer here before considering the skill output complete.
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: 471kUpdated 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