How to Migrate PM Skills from Claude Code to OpenAI Codex

PM Skills can be migrated from Claude Code to OpenAI Codex because the repository stores all core logic in platform-agnostic markdown files, with only the slash-command interface requiring adaptation.

The phuryn/pm-skills repository functions as a Claude Code marketplace for product management workflows, yet its architecture deliberately separates data from execution. Because skills are defined in universal markdown format rather than Claude-specific code, you can migrate PM Skills to OpenAI Codex or other AI assistants with minimal friction.

Why PM Skills Are Platform-Agnostic

The repository's design centers on plain markdown skill files located in pm-*/skills/*.md paths. According to the README in phuryn/pm-skills, these files follow a universal skill format that works with any tool capable of reading structured markdown prompts. This means the core intellectual property—the product management methodologies, examples, and prompt structures—exists independently of Claude Code's execution environment.

Understanding the Migration Architecture

The Marketplace Manifest

The entry point for migration is .claude-plugin/marketplace.json, which lists all available plugins including pm-product-discovery, pm-go-to-market, and others. This JSON file specifies each plugin's source path and category, enabling any AI platform that understands the open Claude Code schema to ingest the complete plugin set programmatically.

Skills vs. Commands

The architecture distinguishes between two distinct components:

• Skills are markdown files containing structured prompts and examples (e.g., pm-product-discovery/skills/brainstorm-ideas-new/SKILL.md) that require no modification to work in Codex.
• Commands are Claude-specific slash commands like /discover and /plan-launch defined in pm-*/commands/*.md files that interpret user input within Claude Code or Cowork.

While commands don't transfer automatically, the underlying skills they invoke remain fully functional when called directly.

Step-by-Step Migration Process

Method 1: Codex CLI Installation

For OpenAI Codex, migration mirrors the native Claude Code installation workflow. First, register the marketplace, then install individual plugins by referencing the pm-skills namespace.

# Add the PM Skills marketplace to Codex

codex plugin marketplace add phuryn/pm-skills

# Install specific plugins (example: product discovery & strategy)

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

Method 2: Manual Skill Extraction

For AI platforms that only read markdown without marketplace support, manually copy the skill directories. Extract the skills/ folders from each plugin directory into your target assistant's skill path.

# Copy skills for platforms like OpenCode that read markdown directly

for plugin in pm-*/; do
  mkdir -p .opencode/skills/
  cp -r "$plugin/skills/"* .opencode/skills/ 2>/dev/null
done

Handling Claude-Specific Commands in Codex

Since Codex does not recognize Claude's slash-command syntax, you must adapt the command layer. Rather than invoking /discover, prompt Codex directly using natural language to execute the underlying skill files.

# Using a skill directly in Codex (no slash command needed)

> Run a product discovery on AI-powered meeting summarizer:
> - brainstorm ideas
> - map assumptions
> - prioritize risky ones
> - design experiments

Alternatively, convert the command definitions from files like pm-product-discovery/commands/discover.md into Codex-compatible skill files by asking the assistant to reinterpret the command logic as standalone prompts.

Summary

• PM Skills stores all core functionality in platform-agnostic markdown files (skills/*.md) that transfer without modification.
• The .claude-plugin/marketplace.json manifest enables automated installation on any platform supporting the Claude Code schema.
• Skills (markdown prompts) migrate automatically, while Commands (Claude-specific slash commands) require natural-language adaptation or conversion.
• Use codex plugin marketplace add for seamless Codex integration, or manually copy skill files to .opencode/skills/ for generic AI assistants.

Frequently Asked Questions

Do I need to rewrite the skill files to use them in Codex?

No. The skill markdown files in pm-*/skills/ directories contain no Claude-specific code—only structured prompts and examples. As implemented in phuryn/pm-skills, these files follow a universal format compatible with any AI assistant that reads markdown, including Codex.

Will slash commands like /discover work in OpenAI Codex?

No. Slash commands defined in files like pm-product-discovery/commands/discover.md are interpreted exclusively by Claude Code and Cowork. In Codex, invoke the same functionality by referencing the skill name directly in natural language or by converting the command logic into a Codex-compatible skill definition.

Can I use PM Skills with AI assistants other than Claude Code and Codex?

Yes. Because the core logic resides in plain markdown files, you can import the skills/ directories into any AI platform that supports markdown-based skill definitions, including OpenCode and custom agent frameworks. Simply copy the relevant skill folders to your assistant's designated skill directory.

How does the marketplace.json file facilitate migration?

The .claude-plugin/marketplace.json file serves as the canonical registry of all plugins, listing metadata and source paths for pm-product-discovery, pm-go-to-market, and other modules. Any AI platform implementing the open Claude Code marketplace schema can parse this file to automatically install the complete plugin ecosystem without manual file manipulation.

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