gtm-strategy
by phurynUse gtm-strategy to build a practical go-to-market strategy for product launches, new segments, and repositioning. The gtm-strategy skill helps you define channels, messaging, success metrics, and launch timing from clear product and market inputs. It is especially useful for Product Marketing teams that need a structured GTM plan, not a generic outline.
This skill scores 74/100, which means it is listable but best treated as a moderately strong, not best-in-class, install. Directory users get a real GTM workflow with clear triggers, stepwise guidance, and practical launch-planning scope, but they should expect some adoption friction because the repository has no supporting scripts, references, or install command to deepen execution.
- Clear triggerability: the description explicitly covers product launch, GTM planning, new market launches, and go-to-market strategy work.
- Operational workflow is present: the skill outlines research gathering, channel selection, messaging, metrics, and launch planning steps.
- Good directory relevance: the body is substantial, with multiple headings and no placeholder markers, suggesting real use-case content rather than a stub.
- Execution support is thin: there are no scripts, references, resources, or rules files to reduce guesswork beyond the markdown instructions.
- Installability is less obvious: no install command is provided in SKILL.md, so users may need extra interpretation to adopt it cleanly.
Overview of gtm-strategy skill
What gtm-strategy does
The gtm-strategy skill helps you turn product and market inputs into a practical go-to-market plan. It is built for people who need more than a generic launch outline: product marketers, founders, PMs, and growth teams planning a new release, entering a new segment, or tightening a launch plan.
Best fit for Product Marketing
Use gtm-strategy for Product Marketing when you need structured decisions on channels, positioning, messaging, launch timing, and success metrics. It is most useful when the goal is to align a launch around a target audience and a measurable outcome, not to write polished copy in isolation.
What makes it useful
The main value of gtm-strategy is that it pushes the work through a sequence: research inputs, channel choice, messaging, and launch planning. That makes it easier to spot gaps early, especially when the product, audience, or competitive context is still fuzzy.
How to Use gtm-strategy skill
Install and inspect the skill
Use the skill install flow in your directory environment, then open the skill file first. In this repo, the key entry point is pm-go-to-market/skills/gtm-strategy/SKILL.md. Because there are no supporting scripts or reference folders, the skill is intentionally lightweight and depends on the quality of your prompt and inputs.
Feed it the right input
The gtm-strategy usage works best when you provide a clear product brief, target segment, market context, and launch constraint. Strong inputs look like:
- product summary and core features
- target buyer or user segment
- problem statement and current alternative
- pricing or packaging context
- launch window, region, or channel limits
- any research, interviews, or competitor notes
If you only say “make a GTM plan,” the output will be broad. If you specify “launch a B2B workflow tool for RevOps teams in mid-market SaaS with a 6-week window,” the skill can make sharper choices.
A practical prompt pattern
For best gtm-strategy usage, ask for a launch plan that includes audience, positioning, channels, timeline, and metrics. A useful prompt should say what changed, who it is for, and what success means. For example: “Create a gtm-strategy guide for a new AI note-taking feature aimed at sales managers. Prioritize low-cost channels, define the core message, and propose launch metrics for the first 30 days.”
Read the file in order
Start with SKILL.md to understand the workflow, then reuse the structure in your own context. Since this skill does not ship with extra resources, the most important reading task is to map each step to your own product facts before generating output.
gtm-strategy skill FAQ
Is gtm-strategy only for new product launches?
No. The gtm-strategy skill also fits new segments, repositioning efforts, and launches where the main challenge is deciding what to say, where to show up, and how to measure traction.
How is this different from a normal prompt?
A normal prompt usually produces a single-pass plan. The gtm-strategy skill encourages a more complete decision path: research first, then channel fit, then messaging, then metrics and rollout timing. That structure improves consistency when the launch has multiple stakeholders.
Do I need to be a Product Marketing expert?
No. gtm-strategy can help beginners by giving them a sensible planning scaffold. But you still need to supply the real product and market inputs; otherwise the output may look polished but stay too generic to use.
When should I not use it?
Skip gtm-strategy if you only need one narrow artifact, like a tagline or one email. It is better for planning the launch system than for writing isolated assets.
How to Improve gtm-strategy skill
Give it sharper market facts
The biggest quality lift comes from better inputs: customer pain, segment definition, competitor alternatives, and any proof points. If you know the audience is “mid-market fintech ops teams that already use Jira and Slack,” say that explicitly. The gtm-strategy skill can only make tradeoffs when the target is concrete.
Ask for decision-ready outputs
Do not ask for a generic strategy summary. Ask for deliverables you can act on: channel priorities, messaging hierarchy, launch phases, risks, and success metrics. The more you frame the output around decisions, the less editing you will need later.
Iterate on gaps, not on style
If the first output feels thin, refine the missing inputs rather than asking for a rewrite. Common weak spots are segment definition, competitive differentiation, and measurement. Re-run the gtm-strategy skill with those specifics added, and the plan will usually become more credible and easier to execute.