# How to Generate a GTM Strategy with PM Skills: A Complete Guide for Product Managers > Learn how to generate a GTM strategy using PM skills with this comprehensive guide. Orchestrate markdown-based skills via the plan-launch command for structured launch plans. - Repository: [Pawel Huryn/pm-skills](https://github.com/phuryn/pm-skills) - Tags: how-to-guide - Published: 2026-06-20 --- **PM Skills is a modular, command-driven toolkit that generates end-to-end Go-to-Market strategies by orchestrating markdown-based skills through the `plan-launch` command, producing structured documents covering market selection, channel mix, messaging, and launch timelines.** The **phuryn/pm-skills** repository provides a plugin-first framework that enables product managers to generate a GTM strategy with PM Skills through composable knowledge modules. This open-source toolkit separates domain knowledge from execution logic, allowing you to produce launch-ready documents by chaining specialized skills with CLI-style commands. ## Understanding the PM Skills Architecture The repository follows a **plugin-first** architecture where each capability is encapsulated as a self-contained markdown file. **Skills** are defined in [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) files that expose metadata including `description`, `inputs`, and `outputs`, while **commands** orchestrate these skills into executable workflows. The orchestrator implemented in the `pm-toolkit` core reads these definitions at runtime, resolves dependencies, and stitches LLM-generated responses into coherent deliverables. ## Core Components of the GTM Workflow The GTM generation capability resides in the **pm-go-to-market** package, which combines high-level strategy templates with execution commands. ### The GTM Strategy Skill Located at [`pm-go-to-market/skills/gtm-strategy/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/gtm-strategy/SKILL.md), this markdown-based skill defines the expected output structure for a complete Go-to-Market plan. It specifies sections covering market selection, channel mix, messaging frameworks, success metrics, and launch timelines. The skill metadata declares contexts where it applies, such as "planning a product launch" or "creating a GTM plan from scratch," enabling the orchestrator to invoke it appropriately. ### The Plan-Launch Command The [`pm-go-to-market/commands/plan-launch.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/commands/plan-launch.md) file implements the primary interface for GTM generation. This command coordinates multiple supporting skills to build a comprehensive strategy package. The workflow executes sequentially: 1. Identify the **beachhead segment** (first-adopter market). 2. Define the **Ideal Customer Profile (ICP)**. 3. Craft **messaging** aligned with product-market fit. 4. Select **GTM motions** (inbound, outbound, PLG) and channels. 5. Produce a **launch timeline** with success metrics. ## Supporting Skills for Market Strategy The modular design enables reuse of individual components across different commands and contexts. ### Ideal Customer Profile Generation The [`pm-go-to-market/skills/ideal-customer-profile/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/ideal-customer-profile/SKILL.md) module generates structured ICP descriptions based on market inputs. This skill can be invoked independently or as part of the `plan-launch` workflow to define target buyer personas and firmographic criteria. ### Beachhead Segment Identification Defined in [`pm-go-to-market/skills/beachhead-segment/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/beachhead-segment/SKILL.md), this skill identifies first-adopter markets and early-v segments. It returns structured criteria for selecting initial launch targets before broader market expansion. ### GTM Motions and Channel Mix The [`pm-go-to-market/skills/gtm-motions/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/gtm-motions/SKILL.md) module recommends channel strategies including inbound marketing, outbound sales, and product-led growth (PLG) motions. It analyzes product characteristics and ICP data to suggest optimal distribution channels. ### Growth Loops Analysis Located at [`pm-go-to-market/skills/growth-loops/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/growth-loops/SKILL.md), this skill maps sustainable growth mechanisms and viral loops that can be embedded into the GTM strategy to drive organic adoption post-launch. ## Executing GTM Generation Commands To generate a GTM strategy with PM Skills, invoke the CLI commands through the PM Skills wrapper. The orchestrator processes natural language prompts, resolves skill dependencies, and returns markdown-formatted deliverables. Generate a complete strategy for a new product: ```bash /plan-launch "Create a GTM strategy for an AI-analytics platform targeting early-stage B2B SaaS founders." ``` Focus on specific GTM motions when you already have ICP and messaging defined: ```bash /gtm-motions "Suggest the best mix of inbound, outbound, and PLG channels for a B2B AI product." ``` Build a beachhead segment definition for niche markets: ```bash /beachhead-segment "Identify the ideal beachhead market for a tele-health diagnostics app." ``` Advanced users can compose multiple skills manually by piping structured data between commands, enabling custom workflows that combine ICP generation, motion selection, and strategy documentation. ## Summary - **PM Skills** uses a modular architecture separating knowledge (skills) from behavior (commands) to generate GTM strategies. - The **`plan-launch`** command orchestrates the complete workflow by chaining skills for beachhead segments, ICPs, messaging, and channel selection. - Skills are self-contained markdown files with metadata located in `pm-go-to-market/skills/*/SKILL.md` that declare inputs, outputs, and contextual applicability. - The toolkit produces ready-to-share markdown documents suitable for product docs, pitch decks, or internal wikis without manual stitching of research components. ## Frequently Asked Questions ### What is PM Skills and how does it help product managers? PM Skills is an open-source, command-driven toolkit that helps product managers generate end-to-end deliverables by chaining modular knowledge modules (skills) with execution commands. It automates the creation of structured documents like GTM strategies, PRDs, and growth plans through LLM-backed orchestration while maintaining consistency via markdown-based templates. ### How does the `plan-launch` command generate a GTM strategy? The `plan-launch` command reads its definition from [`pm-go-to-market/commands/plan-launch.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/commands/plan-launch.md) and executes a sequence of skill invocations including beachhead segment identification, ICP generation, messaging creation, and GTM motion selection. It aggregates the outputs from these individual skills into a cohesive strategy document covering market selection, channel mix, and launch timelines. ### Can I use individual GTM skills without running the full plan-launch workflow? Yes, each skill can be invoked independently using its specific command such as `/beachhead-segment`, `/ideal-customer-profile`, or `/gtm-motions`. This modularity allows you to generate specific components of a GTM strategy when you already have other elements defined, or to reuse these skills in custom command pipelines. ### What file format does PM Skills use for skill definitions? PM Skills uses markdown files named [`SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/SKILL.md) to define skills, with each file containing both human-readable documentation and structured metadata. These files reside in their respective package directories (e.g., [`pm-go-to-market/skills/gtm-strategy/SKILL.md`](https://github.com/phuryn/pm-skills/blob/main/pm-go-to-market/skills/gtm-strategy/SKILL.md)) and declare inputs, outputs, and contextual triggers that the orchestrator uses to determine when and how to invoke the skill.