Go-to-Market Skills and Commands in the PM Skills Marketplace: A Complete Guide

The PM Skills Marketplace ships six markdown-based GTM skills and three slash commands that let product managers generate launch plans, ideal customer profiles, and competitive battlecards via the phuryn/pm-skills repository.

The pm-go-to-market module in the open-source phuryn/pm-skills repository provides a structured toolkit for product managers preparing launch-phase go-to-market (GTM) efforts. These assets are stored as plain-text Markdown files, making them version-controllable, language-agnostic, and extensible without code changes. This guide covers the available skills, executable commands, and implementation patterns found in the source code.

Available Go-to-Market Skills in the PM Skills Marketplace

The module defines six reusable skills—each a self-contained Markdown asset that encapsulates product-management methodologies. Each skill resides in its own subdirectory under pm-go-to-market/skills/ and follows a standardized SKILL.md format.

• beachhead-segment – Evaluates candidate market segments against burning pain, willingness-to-pay, winnable market share, and referral potential to select the optimal initial launch segment. Source: pm-go-to-market/skills/beachhead-segment/SKILL.md.

• ideal-customer-profile – Synthesizes demographics, behaviors, jobs-to-be-done, and pain points into a detailed ICP definition. Use this when defining target customers for product-market-fit surveys or qualifying sales leads. Source: pm-go-to-market/skills/ideal-customer-profile/SKILL.md.

• gtm-strategy – Produces a full GTM plan encompassing channel selection, messaging, success metrics, launch timeline, and risk mitigation. Source: pm-go-to-market/skills/gtm-strategy/SKILL.md.

• gtm-motions – Identifies suitable GTM motions (product-led, sales-led, channel-partner) and the tooling required for each. This skill activates after the beachhead segment is secured. Source: pm-go-to-market/skills/gtm-motions/SKILL.md.

• growth-loops – Maps sustainable “flywheel” mechanisms that turn acquisition, activation, retention, and referral into a self-reinforcing engine. Source: pm-go-to-market/skills/growth-loops/SKILL.md.

• competitive-battlecard – Generates a sales-ready battlecard contrasting your product with a named competitor, including positioning, feature gaps, and objection handling. Source: pm-go-to-market/skills/competitive-battlecard/SKILL.md.

All six skills are enumerated in the pm-go-to-market/README.md file with short descriptions and usage contexts.

Go-to-Market Commands for Rapid Execution

The module exposes three commands—CLI-style slash commands that orchestrate one or more skills to produce immediate outputs. Each command is defined in pm-go-to-market/commands/ as a Markdown file containing execution logic and argument schemas.

Command	Triggered Action	Source File
/plan-launch	Orchestrates the beachhead-segment, ideal-customer-profile, and gtm-strategy skills to output a complete launch plan.	pm-go-to-market/commands/plan-launch.md
/growth-strategy	Stitches together growth-loops and gtm-motions to produce a post-launch growth roadmap.	pm-go-to-market/commands/growth-strategy.md
/battlecard	Invokes the competitive-battlecard skill to generate a one-page competitor comparison.	pm-go-to-market/commands/battlecard.md

These commands are also registered in the module’s README under the Commands section, enabling discovery by the PM-Toolkit runtime.

How the Skills and Commands Work Together

The architectural flow inside the phuryn/pm-skills repository follows a six-step pipeline that transforms slash-command input into structured Markdown output.

1. Command entry – The runtime parses a slash command (/plan-launch, /growth-strategy, or /battlecard).

2. Skill selection – The command internally references one or more skill Markdown files. The runtime loads the skill’s front-matter (name, description) and its procedural steps.

3. Argument injection – The command supplies $ARGUMENTS (product descriptions, research artifacts, etc.) to the skill template.

4. Skill execution – The skill’s templated steps are processed; conditional logic (e.g., “If you have a beachhead segment, invoke the beachhead-segment skill”) is applied.

5. Output synthesis – The final response is a Markdown document containing tables, bullet-point recommendations, and next-step prompts (see the “Generate GTM Plan” block in plan-launch.md).

6. Follow-up hooks – The tail of each command offers quick-action suggestions (e.g., “Want me to design growth loops?”) that map to other commands, creating a chained workflow.

Because all assets are plain-text Markdown, they require no compilation or deployment—adding a new GTM skill only requires a new SKILL.md file and a thin wrapper command.

Practical Usage Examples

Invoke these commands inside any conversation or terminal that supports the PM-Toolkit slash-syntax.

# Generate a full launch plan

/plan-launch AI-powered proposal writer for consulting firms

# Design sustainable growth loops post-launch

/growth-strategy New enterprise tier for our project-management tool

# Create a competitor battlecard for sales enablement

/battlecard Compare our SaaS product vs Competitor X

Each command returns a richly formatted Markdown document (refer to plan-launch.md for the exact output layout).

For programmatic integration, call the toolkit via HTTP:

import requests

# Invoke the plan-launch command via the PM-Toolkit endpoint

payload = {
    "command": "/plan-launch",
    "arguments": "AI-powered proposal writer for consulting firms"
}
resp = requests.post("https://api.productcompass.pm/execute", json=payload)
print(resp.json()["output_markdown"])

The actual endpoint is defined by the host environment; the payload shape illustrates the interface expected by the pm-go-to-market command handlers.

Summary

• The PM Skills Marketplace provides six specialized go-to-market skills stored as Markdown files in pm-go-to-market/skills/.
• Three slash commands—/plan-launch, /growth-strategy, and /battlecard—orchestrate these skills to generate launch plans, growth roadmaps, and competitive battlecards.
• All skills and commands are defined in plain-text Markdown under pm-go-to-market/, making them fully version-controllable and extensible without code changes.
• The execution flow follows a six-stage pipeline: command entry, skill selection, argument injection, skill execution, output synthesis, and follow-up hooks.

Frequently Asked Questions

What are the core go-to-market skills available in the PM Skills Marketplace?

The marketplace includes six skills: beachhead-segment for market selection, ideal-customer-profile for ICP definition, gtm-strategy for full launch planning, gtm-motions for motion selection, growth-loops for sustainable traction design, and competitive-battlecard for sales enablement. Each is implemented as a SKILL.md file in the pm-go-to-market/skills/ directory.

How do I execute a go-to-market command in the PM Skills Marketplace?

Type the slash command followed by your product context. For example: /plan-launch AI-powered proposal writer for consulting firms. The runtime parses the command, loads the relevant skills from pm-go-to-market/commands/, and returns a Markdown output document.

Can I extend the go-to-market module with custom skills?

Yes. Because the architecture relies on plain-text Markdown, you can add a new skill by creating a SKILL.md file in pm-go-to-market/skills/ and a corresponding wrapper command in pm-go-to-market/commands/. No compilation or code deployment is required; the PM-Toolkit runtime discovers new assets automatically.

Where are the skill definitions stored in the repository?

Skill definitions reside in pm-go-to-market/skills/<skill-name>/SKILL.md. Command definitions are stored in pm-go-to-market/commands/<command-name>.md. The module’s entry point and registry are located at pm-go-to-market/README.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}