What is developing-gtm-strategy?

A workflow for creating a go-to-market plan: which customer groups to target, how to reach them, and what to do during the first 90 days after launch. It builds on earlier product-market-fit and market research.

Use it to define ideal customer profiles, rank customer segments and marketing or sales channels, and create a sequenced 90-day launch roadmap.

A product can have a plausible market without having a clear launch audience or distribution plan. This workflow turns research into prioritized segments, channels, and milestones.

developing-gtm-strategy — Skill by qte77

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/qte77/claude-code-plugins/developing-gtm-strategy

Any agent

npx skills add qte77/claude-code-plugins --skill developing-gtm-strategy

Clone the repo

git clone --depth 1 https://github.com/qte77/claude-code-plugins

Made for: Claude Code, Codex.

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 777 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00044	$0.00777
Opus 5	$0.00022	$0.00388
Sonnet 5	$0.00009	$0.00155
Haiku 4.5	$0.00004	$0.00078

Measured 2d ago against content hash c3714ed2abb6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

developing-gtm-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/market-research/skills/developing-gtm-strategy/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Developing GTM Strategy (Phase 3)

Target: $ARGUMENTS

Phase 3 of the GTM pipeline. Depends on Phase 2. Builds the actionable GTM plan: customer segmentation, ICP definition, channel strategy, and launch milestones.

Mode Awareness

Read config/mode.md before starting:

concise — Top segment, top 2 channels, 90-day milestones (bullet list)
detailed — Full ICP profiles, channel analysis matrix, sequenced roadmap
conservative — Proven channels (inbound, direct sales, partnerships); minimize burn
ambitious — Multi-channel blitz, community-led + product-led hybrid, aggressive land-and-expand

Inputs

results/phase-2/pmf-assessment.md — PMF score and risk register
results/phase-1b/market-analysis.md — Buyer personas and market sizing
results/phase-1a/competitor-map.md — Competitor channel strategies
config/comments_gtm.md — GTM preferences and constraints
config/mode.md — Style and approach settings

Workflow

Read Phase 2 PMF output — Use recommendation and risk register to shape strategy
Define customer segments — Prioritize 1-3 segments with ICP definitions
Select GTM channels — Evaluate and rank by reach/cost/fit for each segment
Define positioning — One-liner, value prop, key proof points per segment
Build 90-day launch plan — Milestones, owners, success metrics
Validate against criteria — Check config/validation_criteria.md Phase 3 gates

Output

Write to results/phase-3/:

`gtm-strategy.md`

# GTM Strategy

## Target Segments

### Segment 1: [Name]
- ICP: [job title, company size, industry, trigger event]
- Pain: [primary pain]
- Value prop: [one sentence]
- Proof point: [evidence or analogy]

## Channel Strategy

| Channel | Reach | Cost | Fit | Priority |
|---------|-------|------|-----|----------|
| [channel] | H/M/L | H/M/L | H/M/L | 1/2/3 |

## Positioning

### One-Liner
"[Product] is the [category] for [segment] that [differentiator]."

### Key Proof Points
1. [proof point]

## 90-Day Launch Plan

| Week | Milestone | Owner | Success Metric |
|------|-----------|-------|----------------|
| 1-2  | [milestone] | [role] | [metric] |
| 3-6  | [milestone] | [role] | [metric] |
| 7-12 | [milestone] | [role] | [metric] |

Read the full file on GitHub · 90 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 90 lines · 44 tokens per session scan A c3714ed2abb6

Subscribe to this mod's changes

developing-gtm-strategy is a skill published in the GitHub repository qte77/claude-code-plugins (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 44 tokens to every session and 777 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Marketing and SEO agent-skills ai-coding-tools claude-code claude-code-marketplace claude-code-plugins claude-code-skills

orchestrator

FULLY AUTONOMOUS Flutter development pipeline orchestrator. Smart routing: PM analyzes -> creates targeted tasks -> Orchestrator executes only needed agents. Supports Asana task URLs. Includes QE verification via Maestro E2E tests. 7-phase flow: PM -> TodoWrite -> Execute -> Review -> Tests -> QE E2E -> Close.

aleksandr-chaika/flutter-clean-arch-skills · 72 tokens

flutter-guide

Flutter/BLoC Clean Architecture patterns, review checklists, and testing guides. Background knowledge for flutter-dev, flutter-reviewer, flutter-tester. Not user-invocable.

aleksandr-chaika/flutter-clean-arch-skills · 39 tokens

maestro-flutter

Maestro E2E testing knowledge for Flutter apps. YAML-based flows, TestKeys, visual regression, Maestro MCP integration. Background knowledge for QE E2E testing phase.

aleksandr-chaika/flutter-clean-arch-skills · 41 tokens

android-kotlin-compose

Android development with Kotlin and Jetpack Compose. Use when user mentions "Compose", "Jetpack Compose", "Material3", "Hilt", "Room", "ViewModel", or needs to build Android UI, implement MVVM architecture, manage Compose state, or integrate Jetpack libraries (Navigation, Room, Hilt, ViewModel). Triggers on…

and3r817/dot-claude-plugins · 84 tokens

android-kotlin-coroutines

Android development with Kotlin Coroutines and Flow. Use when user mentions "coroutines", "suspend", "Flow", "StateFlow", "SharedFlow", "viewModelScope", "lifecycleScope", or needs to implement async programming, handle structured concurrency, integrate coroutines with Retrofit/Room/WorkManager, or write coroutine…

and3r817/dot-claude-plugins · 87 tokens

codex-advisor

Advisory consultation skill for architectural reviews, design decisions, code analysis, and technology evaluation. Codex provides recommendations without making code changes. Invoked by phrases like "consult Codex", "get Codex's opinion", "ask Codex about", "have Codex review", "Codex analysis", "validate this…

and3r817/dot-claude-plugins · 85 tokens