Agent skill · Workflow & Productivity

go-to-market

Create go-to-market assets for any product or feature. Use when asked for a GTM plan, positioning statement, product launch plan, messaging pillars, use cases, or feature/benefit list. Produces a full GTM pack: positioning statement, messaging pillars, feature-to-benefit mapping, and role-specific use cases. For a tiered launch plan with cross-functional coordination use go-to-market-planner instead.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill go-to-market --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/go-to-market/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Go-To-Market Skill This skill produces a complete go-to-market asset pack for a product, feature, or initiative. It follows Geoffrey Moore's positioning framework and structures all outputs for use in sales decks, landing pages, launch emails, and internal alignment docs. ## Working from a brief You will often get a short brief without every detail. **Always deliver the full GTM pack anyway** — do not stop to ask questions and do not leave bracketed placeholders like `[ADD PROOF POINT]` or `[Technical capability]`. Where a detail is missing (differentiators, proof points, features), infer specific, realistic ones from the product description and the target customer, and mark anything inferred as *(assumed — confirm)*. A concrete, labelled assumption is always better than a blank. ## Inputs (infer any not provided — label assumptions) - **Product/feature name** - **One-line description** (what it does, technically) - **Target customer** (role, company size, industry if relevant) - **Primary problem it solves** - **Key competitor or alternative** (what people do today without this) - **Top 3 differentiators** ## Reads from / Writes to the Brain If a [`professional-brain`](../profes

What's inside
Steps it walks through
  1. Working from a brief
  2. Inputs (infer any not provided — label assumptions)
  3. Reads from / Writes to the Brain
  4. Output Structure
  5. 1. Positioning Statement
  6. 2. Messaging Pillars
  7. 3. Feature & Functionality List
  8. 4. Use Cases
  9. Deeper Materials
  10. Scoring Rubric (0–40)
  11. Quality Checks
  12. Anti-Patterns
  13. Example Trigger Phrases
Ships with 3 files
  • references/messaging-hierarchy.md
  • references/worked-example.md
  • templates/gtm-pack.md
More from pm-claude-skills
All skills →
About this skill
What does the go-to-market skill do?

Create go-to-market assets for any product or feature. Use when asked for a GTM plan, positioning statement, product launch plan, messaging pillars, use cases, or feature/benefit list. Produces a full GTM pack: positioning statement, messaging pillars, feature-to-benefit mapping, and role-specific use cases. For a tiered launch plan with cross-functional coordination use go-to-market-planner instead.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill go-to-market --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going