qte77/developing-gtm-strategy
plugins/market-research/skills/developing-gtm-strategy/SKILL.md
Develop customer segmentation, channel selection, and a 90-day launch plan from Phase 2 PMF assessment. Run after `validating-product-market-fit` (Phase 3).
$ install --global
skillsauthnpx skillsauth add qte77/claude-code-plugins developing-gtm-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 28, 2026, 6:49 AM115.0s1 file scanned
SKILL.md
- name:
- developing-gtm-strategy
- description:
- Develop customer segmentation, channel selection, and a 90-day launch plan from Phase 2 PMF assessment. Run after `validating-product-market-fit` (Phase 3).
- compatibility:
- Designed for Claude Code
- stability:
- development
- allowed-tools:
- Read, Write, Glob, Grep, WebSearch, WebFetch
- argument-hint:
- [product-name]
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 roadmapconservative— Proven channels (inbound, direct sales, partnerships); minimize burnambitious— Multi-channel blitz, community-led + product-led hybrid, aggressive land-and-expand
Inputs
results/phase-2/pmf-assessment.md— PMF score and risk registerresults/phase-1b/market-analysis.md— Buyer personas and market sizingresults/phase-1a/competitor-map.md— Competitor channel strategiesconfig/comments_gtm.md— GTM preferences and constraintsconfig/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.mdPhase 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] |
Rules
- ICP definitions must be specific enough to identify a named prospect
- Channel priority must account for budget tier from
config/comments_gtm.md - Every milestone needs a measurable success metric
- Align positioning against competitor weaknesses from Phase 1A
Related Skills
qte77/triaging-security-report
development
VerifiedTrustedCommunity
Verify an external or AI-generated security report against the actual codebase before acting on it. Use when handed a scanner PDF, automated teardown, audit report, or bug-bounty submission — classifies every finding CONFIRMED / OVERSTATED / FALSE-POSITIVE / FABRICATED and salvages the real work items.
2SKILL.mdUpdated Jul 6, 2026
qte77/auditing-website-seo-geo
development
VerifiedTrustedCommunity
Audits a site's SEO and AI-search (GEO) readiness — meta tags, Open Graph/Twitter, JSON-LD, robots/llms conventions — and generates fixes. Use when reviewing search visibility, social previews, structured data, or LLM/AI-crawler discoverability.
1SKILL.mdUpdated Jun 14, 2026
qte77/writing-readme
documentation
VerifiedTrustedCommunity
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
1SKILL.mdUpdated Apr 19, 2026
qte77/auditing-readme
development
VerifiedTrustedCommunity
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
1SKILL.mdUpdated Apr 19, 2026