How to Use the pm-product-strategy Plugin for Claude: A Complete Guide

The pm-product-strategy plugin is a Claude extension that provides slash commands and reusable skills to guide product managers through structured frameworks like value propositions, business models, and competitive analysis.

The pm-product-strategy plugin, hosted in the phuryn/pm-skills repository, bundles reusable skills and end-to-end commands that transform Claude into a strategic product management assistant. It enables teams to execute structured workflows—from JTBD value propositions to full nine-section strategy canvases—using simple slash commands like /strategy and /value-proposition.

Installation Methods

You can install the pm-product-strategy plugin through three different interfaces depending on your Claude environment.

Claude Cowork (GUI)

Use the visual plugin browser to add the marketplace source and install:

1. Open Customize → Browse plugins → Personal → +
2. Enter phuryn/pm-skills as the marketplace source
3. Select pm-product-strategy to install

Claude Code (CLI)

Run the following commands in your terminal to add the marketplace and install the specific plugin:

# Add the marketplace

claude plugin marketplace add phuryn/pm-skills

# Install the plugin

claude plugin install pm-product-strategy@pm-skills

Codex CLI (OpenAI)

For Codex users, the installation syntax uses slightly different commands:

# Add the marketplace

codex plugin marketplace add phuryn/pm-skills

# Install the plugin

codex plugin add pm-product-strategy@pm-skills

Note: Installation details are documented in the repository README at README.md#installation.

Core Commands and Workflows

The pm-product-strategy plugin exposes five primary slash commands that orchestrate multiple skills into complete workflows. Each command is defined in the pm-product-strategy/commands/ directory and follows the pattern /<command> [optional argument].

Value Proposition Command

The /value-proposition command (defined in pm-product-strategy/commands/value-proposition.md) guides users through a six-part Jobs-to-Be-Done (JTBD) framework.

Invocation example:

/value-proposition AI-powered writing assistant for non-native English speakers

Workflow steps:

1. Collect product description or uploaded documents
2. Prompt for the six JTBD elements: Who, Why, What Before, How, What After, and Alternatives
3. Render a markdown template based on lines 34-48 of the command file

Sample output:

## Value Proposition: AI Writing Assistant

### For Early-stage Founders:

1. **Who**: founders who write investor updates.
2. **Why**: they need concise, persuasive copy quickly.
3. **What Before**: manual drafting takes hours, leads to sloppy language.
4. **How**: AI suggests phrasing, structure, and tone in real-time.
5. **What After**: updates are polished in minutes, boosting confidence.
6. **Alternatives**: generic writing tools; they lack domain-specific guidance.

**Value Proposition Statement**  
For founders who need fast investor updates, **AI Writing Assistant** is an AI-powered copywriter that produces polished drafts instantly. Unlike generic AI writers, we specialize in VC-ready language.

Strategy Command

The /strategy command (defined in pm-product-strategy/commands/strategy.md) generates a full nine-section Product Strategy Canvas by leveraging the product-strategy and product-vision skills.

Invocation example:

/strategy B2B project-management platform for agency teams

Workflow steps:

1. Gather context including product description, stage, and business model
2. Iterate through nine sections (Vision → Defensibility) using the underlying skills
3. Output a ready-to-share markdown document (see lines 39-94 of the command file)

Sample output structure:

## Product Strategy: Agency PM Platform

**Date**: 2026-06-20
**Stage**: MVP
**Author**: <user>

### 1. Vision

Enable agency teams to deliver projects 30% faster while keeping clients delighted.

### 2. Target Segments

| Segment | Size | Pain Level | Current Alternative | Priority |
|---------|------|-----------|---------------------|----------|
| Mid-size agencies (10-50 employees) | 5M | High | Manual spreadsheets | 1 |

### Strategic Risks

1. Low adoption due to entrenched spreadsheet habits.
2. Integration complexity with existing agency tools.

### Next Steps

- Share the canvas with the leadership team.
- Validate assumptions with 5 pilot agencies.

Business Model Command

The /business-model command (defined in pm-product-strategy/commands/business-model.md) explores multiple canvas types including Lean Canvas, Full Business Model Canvas, Startup Canvas, and Value Proposition Canvas.

Invocation example:

/business-model startup — AI-writing tool

Claude guides users through selecting a canvas type, then invokes the appropriate skill (such as lean-canvas or business-model) to populate the framework.

Market Scan Command

The /market-scan command (defined in pm-product-strategy/commands/market-scan.md) conducts a comprehensive macro-environment analysis by chaining four distinct skills:

• swot-analysis for internal and external factors
• pestle-analysis for political, economic, social, technological, legal, and environmental factors
• porters-five-forces for competitive dynamics
• ansoff-matrix for growth strategy options

Invocation example:

/market-scan SaaS productivity app

Pricing Command

The /pricing command (defined in pm-product-strategy/commands/pricing.md) builds pricing strategies by calling the pricing-strategy skill and prompting for willingness-to-pay data.

Invocation example:

/pricing AI-design assistant

The workflow produces a pricing recommendation including models, competitive analysis, and proposed experiments.

Plugin Architecture and Source Files

Understanding the file structure helps you customize or debug the pm-product-strategy plugin. The plugin resides in the pm-product-strategy/ directory and contains three core components:

Plugin Metadata

The pm-product-strategy/.claude-plugin/plugin.json file contains metadata including name, version, author, and keywords that allow Claude to discover and register the plugin.

Skills Directory

The pm-product-strategy/skills/ folder contains markdown files that define reusable frameworks. Each skill is a self-contained knowledge source that Claude can invoke automatically:

• pm-product-strategy/skills/value-proposition/SKILL.md – Defines the six-part JTBD template
• pm-product-strategy/skills/product-strategy/SKILL.md – Describes the nine-section Strategy Canvas
• pm-product-strategy/skills/lean-canvas/SKILL.md – Business model framework definitions

Commands Directory

The pm-product-strategy/commands/ folder contains slash-command definitions that orchestrate skills into workflows:

• pm-product-strategy/commands/value-proposition.md – JTBD value proposition workflow
• pm-product-strategy/commands/strategy.md – Full product strategy canvas
• pm-product-strategy/commands/business-model.md – Business model exploration
• pm-product-strategy/commands/market-scan.md – Competitive analysis workflow
• pm-product-strategy/commands/pricing.md – Pricing strategy builder

Chaining Commands for Advanced Workflows

You can execute commands sequentially to build upon previous context. Claude retains session information, allowing you to refine strategy documents without re-entering base assumptions.

Example workflow:

/strategy SaaS analytics dashboard for e-commerce
... (receive strategy document) ...
/business-model startup — SaaS analytics dashboard

Claude automatically reuses segments and value propositions from the previous /strategy output when generating the business model canvas, reducing redundancy and ensuring strategic alignment.

Summary

• The pm-product-strategy plugin transforms Claude into a structured product management assistant through five core slash commands.
• Installation supports three methods: Claude Cowork GUI, Claude Code CLI (claude plugin install pm-product-strategy@pm-skills), and Codex CLI (codex plugin add pm-product-strategy@pm-skills).
• Commands include /strategy for nine-section canvases, /value-proposition for JTBD frameworks, /business-model for canvas exploration, /market-scan for competitive analysis, and /pricing for pricing strategies.
• Source files are organized into plugin.json (metadata), skills/ (framework definitions), and commands/ (workflow orchestrations).
• Chaining commands allows you to build comprehensive strategy documents while reusing context across sessions.

Frequently Asked Questions

How do I update the pm-product-strategy plugin to the latest version?

Run the install command again using the CLI method for your environment. For Claude Code, execute claude plugin install pm-product-strategy@pm-skills; for Codex, use codex plugin add pm-product-strategy@pm-skills. The package manager will pull the latest version from the phuryn/pm-skills marketplace and overwrite the existing plugin files.

Can I modify the skills or commands to fit my company's specific frameworks?

Yes. The plugin uses plain markdown files for skills and commands. Navigate to pm-product-strategy/skills/ or pm-product-strategy/commands/ in your installation directory, edit the relevant .md files (such as SKILL.md or strategy.md), and restart Claude. Changes to the JTBD template in value-proposition/SKILL.md or the canvas sections in strategy.md will take effect immediately for subsequent invocations.

What is the difference between a skill and a command in the pm-product-strategy plugin?

Skills are reusable knowledge units stored in pm-product-strategy/skills/ that define specific frameworks (like SWOT analysis or Lean Canvas). Commands are user-facing workflows stored in pm-product-strategy/commands/ that orchestrate one or more skills into complete interactive sessions. You invoke commands with slash syntax (e.g., /strategy), while skills are automatically called by Claude when processing those commands.

Does the plugin work with both Claude Code and standard Claude web interface?

The pm-product-strategy plugin supports Claude Cowork (the GUI/web interface), Claude Code (the CLI tool), and Codex CLI. The GUI installation uses the plugin browser under Customize → Browse plugins, while CLI installations use the claude plugin or codex plugin commands. All five core commands function identically across interfaces once installed.

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