Launch Strategy
freekmurze/dotfiles
When the user wants to plan a product launch, feature announcement, or release strategy.
Build a go-to-market plan for any product launch, feature release, or new market entry.
Install Go To Market Planner
$ npx skills add mohitagw15856/pm-claude-skills --skill go-to-market-planner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills go-to-market-planner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/go-to-market-planner .claude/skills/go-to-market-planner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "go-to-market-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/go-to-market-planner into .claude/skills/go-to-market-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-to-market-planner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/go-to-market-plannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill go-to-market-planner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills go-to-market-planner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/go-to-market-planner .agents/skills/go-to-market-planner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "go-to-market-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/go-to-market-planner into .agents/skills/go-to-market-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-to-market-planner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill go-to-market-planner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills go-to-market-planner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/go-to-market-planner .cursor/skills/go-to-market-planner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "go-to-market-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/go-to-market-planner into .cursor/skills/go-to-market-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-to-market-planner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/go-to-market-planner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill go-to-market-planner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills go-to-market-planner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/go-to-market-planner .gemini/skills/go-to-market-planner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "go-to-market-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/go-to-market-planner into .gemini/skills/go-to-market-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-to-market-planner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills go-to-market-plannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill go-to-market-planner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/go-to-market-planner .github/skills/go-to-market-planner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "go-to-market-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/go-to-market-planner into .github/skills/go-to-market-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-to-market-planner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill go-to-market-planner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills go-to-market-planner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/go-to-market-planner .opencode/skills/go-to-market-planner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "go-to-market-planner" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/go-to-market-planner into .opencode/skills/go-to-market-planner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "go-to-market-planner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
go-to-market-planner- GitHub stars
- 1.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 666 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a go-to-market plan for any product launch, feature release, or new market entry.
- Works in 7 steps: What We're Launching → Target Audience → Messaging → …
- Planning a product launch
- SKILL.md covers Launch Tier Framework, GTM Plan Output Format, Required Inputs and Guidelines, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Go To Market Planner is an agent skill from mohitagw15856/pm-claude-skills. Build a go-to-market plan for any product launch, feature release, or new market entry. Use when planning a product launch, writing a GTM strategy, defining launch tiers, or coordinating cross-functional launch activities. Produces a tiered GTM plan with messaging, cross-functional activity tracker, success metrics, and launch day checklist. For positioning and messaging content itself use go-to-market instead.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Go-to-market strategy and Product launch strategy. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Planning a product launch
- Writing a GTM strategy
- Defining launch tiers
- Coordinating cross-functional launch activities
Example prompts
- “/go-to-market-planner”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Go To Market Planner loads about 1.4k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 666 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 666 words, ~1,384 tokens.
Download SKILL.mdSave it as
.claude/skills/go-to-market-planner/SKILL.md (or your agent's skills folder).- name
- go-to-market-planner
- description
- Build a go-to-market plan for any product launch, feature release, or new market entry. Use when planning a product launch, writing a GTM strategy, defining launch tiers, or coordinating cross-functional launch activities. Produces a tiered GTM plan with messaging, cross-functional activity tracker, success metrics, and launch day checklist. For positioning and messaging content itself use go-to-market instead.
Go-to-Market Planner Skill
Produce a complete, cross-functional GTM plan that aligns product, marketing, sales, and support around a single launch — with clear owners, timelines, and success metrics.
Launch Tier Framework
Before planning, classify the launch:
| Tier | Scope | Typical Effort | Examples |
|---|---|---|---|
| Tier 1 — Major Launch | New product / significant platform change | 8–12 weeks | New pricing model, platform rebrand, new product line |
| Tier 2 — Feature Launch | Significant new capability | 4–6 weeks | Major feature, API release, new integration |
| Tier 3 — Incremental Release | Improvement, bug fix, minor feature | 1–2 weeks | UI tweak, performance improvement, small enhancement |
Always confirm tier with the user before proceeding.
GTM Plan Output Format
GTM Plan — [Product/Feature Name] — [Launch Date]
Launch Tier: [1 / 2 / 3] Launch Owner (PM): [Name] Target Launch Date: [Date] Soft Launch Date (Beta/Limited): [Date, if applicable]
1. What We're Launching
One-line description: [What it is, for whom, and why now] Key customer problem solved: [Specific pain point] Key differentiator: [Why ours, why now]
2. Target Audience
Primary segment: [Who benefits most — be specific] Secondary segment: [Who else benefits] Not for: [Who this is NOT for — helps sales and support]
3. Messaging
Headline: [Customer-facing headline — lead with outcome, not feature] Sub-headline: [Supporting context — how it works or why it matters] 3 key messages:
- [Problem solved]
- [How it works / what's new]
- [Proof / social proof / data]
Elevator pitch (30 seconds):
[For [target user] who [has this problem], [product/feature] is a [category] that [key benefit]. Unlike [alternative], we [differentiator].]
4. Launch Activities by Function
| Function | Activity | Owner | Due Date | Status |
|---|---|---|---|---|
| Product | Feature flagging / rollout plan | PM | [date] | |
| Marketing | Blog post / landing page | Marketing | [date] | |
| Marketing | Email campaign to existing users | Marketing | [date] | |
| Marketing | Social media content | Marketing | [date] | |
| Sales | Sales enablement deck | PM + Sales | [date] | |
| Sales | FAQ for sales team | PM | [date] | |
| Support | Help centre articles | Support | [date] | |
| Support | Support team training | Support | [date] | |
| Engineering | Monitoring/alerting in place | Eng | [date] |
5. Success Metrics
| Metric | Baseline | Target | Measurement Window |
|---|---|---|---|
| [Adoption metric] | [X] | [Y] | 30 days post-launch |
| [Engagement metric] | [X] | [Y] | 60 days post-launch |
| [Business metric] | [X] | [Y] | 90 days post-launch |
6. Risks & Contingencies
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [Risk] | H/M/L | H/M/L | [Action if it happens] |
7. Launch Day Checklist
- Feature live for [X%] of users
- Monitoring dashboard active
- Support team briefed
- Blog post published
- Email sent / scheduled
- Sales team notified
- Executive announcement sent (if Tier 1)
- Rollback procedure confirmed
Show full SKILL.md (277 more words)Show less
Required Inputs
Ask the user for these if not provided:
- Product or feature name
- Target launch date
- Launch tier (Tier 1 / 2 / 3 — or describe scope and the skill will classify)
- Target audience (who benefits and who it's NOT for)
- Key message (what's the headline outcome for the customer)
- PM and launch owner
Guidelines
- Never plan a Tier 1 launch without at least 8 weeks of lead time
- Always include a "Not for" section — it prevents misdirected sales and support tickets
- Recommend a soft launch to 5–10% of users before full rollout for any Tier 1 or 2 launch
- Post-launch retrospective should be scheduled at launch planning time — don't leave it to chance
Quality Checks
- Launch tier is confirmed and appropriate for scope
- "Not for" section is included to prevent misdirected sales and support
- Every function has at least one activity with a named owner and due date
- Success metrics include a measurement window (30/60/90 days)
- Rollback procedure is confirmed for Tier 1 and 2 launches
- Post-launch retrospective is scheduled
Anti-Patterns
- Do not build a Tier 1 GTM plan for an incremental feature update — tier the launch appropriately before planning
- Do not create activity lists without named owners and due dates — unowned tasks do not get done
- Do not skip the rollback procedure for Tier 1 and 2 launches — every significant launch must have an abort plan
- Do not treat marketing and engineering as separate tracks — cross-functional coordination is the whole point of a GTM plan
- Do not set success metrics without a defined measurement window — "increase signups" is not a measurable target
Example Trigger Phrases
- "Plan a product launch."
- "Write a GTM strategy."
- "Define launch tiers."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/go-to-market-planner of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Go To Market Planner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Go To Market Planner this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Launch Strategyfreekmurze/dotfiles | 1k | 22 repos | ~3.1k | Automated safety check: Pass | None | |
| Marketing StrategistCoWork-OS/CoWork-OS | 480 | — | ~893 | Automated safety check: Pass | MIT | |
| Launch Gtmandreaskelm/pm-brain | 234 | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Go To Marketemotixco/claude-skills-founder | 540 | — | ~884 | Automated safety check: Pass | MIT | |
| Multi-Platform Launch Plannertech-leads-club/agent-skills | 7k | — | ~3.9k | Automated safety check: Pass | Custom licence |
Similar skills
Marketing Strategist
CoWork-OS/CoWork-OS
Comprehensive marketing strategy across 25 disciplines — positioning, copywriting frameworks, buyer psychology, SEO, CRO, paid ads, funnel architecture, content strategy, growth loops, analytics…
Launch Gtm
andreaskelm/pm-brain
Plan, tighten, or review a product launch and go-to-market motion: rollout phases, beta and GA readiness, sales enablement, marketing launch, and release comms (internal and external).
Go To Market
emotixco/claude-skills-founder
Plan a product launch from pre-launch audience building to a 90-day growth plan, with named communities, platform-specific launch tactics, channel rankings, and a budget for $0-$500 a month.
Multi-Platform Launch Planner
tech-leads-club/agent-skills
Plans a product launch across Product Hunt, Hacker News, BetaList and other directories, with timing from the pre-launch waitlist through post-launch follow-up.
Gingiris Go Global
Gingiris-1031/Competitor-analysis-tool
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Go To Market Planner
What does Go To Market Planner do?
Build a go-to-market plan for any product launch, feature release, or new market entry. Go To Market Planner is an agent skill from mohitagw15856/pm-claude-skills. Build a go-to-market plan for any product launch, feature release, or new market entry.
When should I use Go To Market Planner?
Go To Market Planner fits situations like: planning a product launch; writing a GTM strategy; defining launch tiers; coordinating cross-functional launch activities.
How do I install Go To Market Planner in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill go-to-market-planner -a claude-code`. Or copy the skill folder (skills/go-to-market-planner in mohitagw15856/pm-claude-skills) into .claude/skills/go-to-market-planner in your project. Claude Code loads it when a task matches its description.
How do I install Go To Market Planner in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill go-to-market-planner -a codex`. Or copy the skill folder (skills/go-to-market-planner in mohitagw15856/pm-claude-skills) into .agents/skills/go-to-market-planner in your project. Codex loads it when a task matches its description.
Can I use Go To Market Planner in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill go-to-market-planner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/go-to-market-planner, .gemini/skills/go-to-market-planner, .github/skills/go-to-market-planner and .opencode/skills/go-to-market-planner in your project.
What does Go To Market Planner need to run?
SKILL.md names no scripts, command-line tools or credentials: Go To Market Planner is instructions for the agent only.
Does Go To Market Planner access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Go To Market Planner safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Go To Market Planner use?
Go To Market Planner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Go To Market Planner use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Go To Market Planner?
Skills that share tags, products or a category with Go To Market Planner: Launch Strategy (freekmurze/dotfiles, 1k stars), Marketing Strategist (CoWork-OS/CoWork-OS, 480 stars), Launch Gtm (andreaskelm/pm-brain, 234 stars) and Go To Market (emotixco/claude-skills-founder, 540 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Go To Market Planner?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.