How to Install PM Skills Using Codex CLI: A Step-by-Step Guide
Register the PM Skills marketplace with codex plugin marketplace add phuryn/pm-skills, then install individual plugins like pm-toolkit@pm-skills to activate product-management skills in your OpenAI Codex CLI workflow.
The phuryn/pm-skills repository distributes a comprehensive marketplace of product-management plugins that extend the Codex CLI with specialized skills for strategy, discovery, and execution. When you install PM Skills using Codex CLI, you transform the AI assistant into a product-management partner capable of running discovery cycles, crafting PRDs, and prioritizing backlogs through natural language commands.
Understanding the Plugin Architecture
PM Skills Marketplace operates as a distributed plugin system. The central configuration lives in .claude-plugin/marketplace.json, which defines the repository location and available plugin manifests. This file allows both Claude Code and Codex CLI to resolve the phuryn/pm-skills remote and fetch individual plugin bundles.
Each plugin (e.g., pm-toolkit, pm-product-strategy) encapsulates related skills defined in SKILL.md files within skills/ subdirectories. Installing a plugin makes these skills available to Codex, enabling plain-language invocation of complex product workflows.
Step-by-Step Installation Process
Register the Marketplace
First, you must register the remote repository that contains the plugin manifest. This step tells Codex CLI where to find the phuryn/pm-skills definitions.
codex plugin marketplace add phuryn/pm-skills
This command reads the .claude-plugin/marketplace.json file in the repository root and registers the marketplace under the pm-skills namespace.
Install Individual Plugins
After registering the marketplace, install the specific plugin bundles you need. All nine plugins are optional, but installing the core set provides comprehensive coverage.
# Core toolkit with universal utilities
codex plugin add pm-toolkit@pm-skills
# Strategy and planning
codex plugin add pm-product-strategy@pm-skills
codex plugin add pm-product-discovery@pm-skills
codex plugin add pm-market-research@pm-skills
# Data and growth
codex plugin add pm-data-analytics@pm-skills
codex plugin add pm-marketing-growth@pm-skills
# Execution and shipping
codex plugin add pm-go-to-market@pm-skills
codex plugin add pm-execution@pm-skills
codex plugin add pm-ai-shipping@pm-skills
Each command pulls the plugin definition and installs the associated skills into your Codex environment.
Available Plugins and Capabilities
The repository contains nine distinct plugins covering the full product lifecycle:
- pm-toolkit: Universal utilities and base commands
- pm-product-strategy: Vision crafting, roadmap planning, and strategic alignment
- pm-product-discovery: Assumption mapping, user research, and experiment design
- pm-market-research: Competitive analysis and market sizing
- pm-data-analytics: Metrics definition, analytics implementation, and data interpretation
- pm-marketing-growth: Growth strategies, pricing models, and validation experiments
- pm-go-to-market: Launch planning and coordination workflows
- pm-execution: PRD writing, ship checklists, and sprint planning
- pm-ai-shipping: AI-assisted development workflows and rapid prototyping
Using PM Skills After Installation
Once installed, skills become searchable and commands become available immediately. You can invoke complex workflows using natural language prompts.
Run a full discovery cycle:
Run product discovery on a new AI note-taking tool: brainstorm ideas, map assumptions, prioritize the riskiest ones, then design experiments.
Create product strategy documents:
Help me craft a product vision for a SaaS analytics platform.
Execute operational tasks:
Prioritize these feature requests [attach CSV] using impact-effort matrix.
These prompts leverage the SKILL.md definitions located in paths like pm-toolkit/skills/*/SKILL.md and pm-execution/skills/*/SKILL.md, which Codex reads to understand context and required outputs.
Key Source Files in the Repository
Understanding the repository structure helps troubleshoot installation issues:
README.md: Contains the official installation snippet and marketplace documentation under the "Codex CLI (OpenAI)" section.claude-plugin/marketplace.json: The marketplace manifest that Codex CLI consumes to resolve plugin referencespm-toolkit/skills/*/SKILL.md: Skill definitions that provide discovery and research capabilitiespm-execution/skills/*/SKILL.md: Execution-focused skills including/write-prdand/ship-checkcommands
Summary
- Register first: Run
codex plugin marketplace add phuryn/pm-skillsto enable the marketplace resolution - Install selectively: Use
codex plugin add <plugin-name>@pm-skillsto install specific skill bundles (nine available) - Immediate availability: Skills defined in
SKILL.mdfiles become searchable and commands executable without restart - No code changes required: Installation is purely CLI-based; no repository cloning or manual configuration needed
- Cross-platform compatibility: The
.claude-plugin/marketplace.jsonformat works with both Codex CLI and Claude Code
Frequently Asked Questions
What is the difference between adding the marketplace and adding a plugin?
Adding the marketplace with codex plugin marketplace add registers the remote repository location defined in .claude-plugin/marketplace.json, creating a namespace (pm-skills) that Codex can resolve. Adding a plugin with codex plugin add installs a specific skill bundle (like pm-toolkit) from that registered marketplace, making its SKILL.md definitions and commands available to your CLI session.
Can I install only specific plugins without adding the entire marketplace?
No. You must first register the marketplace using codex plugin marketplace add phuryn/pm-skills because the marketplace definition tells Codex CLI where to locate and resolve plugin references. Without this step, the CLI cannot find the pm-skills namespace to install individual plugins.
Where are the skill definitions stored in the repository?
Each plugin stores its skill definitions in SKILL.md files within plugin-specific skills/ directories. For example, pm-toolkit/skills/*/SKILL.md contains discovery utilities, while pm-execution/skills/*/SKILL.md houses execution commands like PRD templates. Codex reads these files to understand the capabilities and context windows for each skill.
Do I need to restart Codex CLI after installing plugins?
No restart is required. According to the phuryn/pm-skills source code, after plugins are added, every skill defined in the relevant SKILL.md files becomes immediately searchable, and you can invoke bundled commands via plain-language prompts right away.
Have a question about this repo?
These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:
curl -s "https://instagit.com/install.md" Maintain an open-source project? Get it listed too →