Do Slash Commands Work with Codex CLI for PM Skills?

No, the /slash commands that ship with PM Skills are Claude-specific and do not function as slash commands in Codex CLI, though the underlying skills remain fully accessible via natural language prompts.

The phuryn/pm-skills repository provides a comprehensive product management toolkit that works across both Claude Code and Codex CLI, but the convenient /discover and /write-prd shortcuts behave differently depending on your environment. While the marketplace installation process is identical, Codex's plugin architecture fundamentally lacks the slash command exposure mechanism that makes these shortcuts possible in Claude.

Why Slash Commands Are Not Supported in Codex

Codex CLI cannot expose PM Skills as slash commands because its plugin system does not support slash-invoked workflows. According to the repository's README.md, the marketplace "reads the same plugin marketplace file as Claude Code, so you can install PM Skills natively" but explicitly notes that "the /slash commands (/discover, /write‑prd, …) install but don’t run as Codex slash commands — Codex plugins don’t expose commands" (lines 82-86).

A later section in the same file reinforces this limitation: "What's different from Claude Code: the /slash commands (/discover, /write‑prd, …) install but don’t run as Codex slash commands" (lines 104-106). This architectural difference means that while the skill definitions are present in your Codex environment, they lack the command-line interface wrapper that Claude provides.

How to Use PM Skills in Codex Without Slash Commands

You can still execute the full product management workflows by invoking the underlying skills directly. The building blocks remain identical; only the invocation method changes.

Install the Plugins

First, add the marketplace and install the required plugins using Codex CLI commands:

codex plugin marketplace add phuryn/pm-skills
codex plugin add pm-toolkit@pm-skills

Invoke Skills via Natural Language

Instead of typing /discover, describe the workflow you want to execute. Codex will automatically invoke the appropriate underlying skills (brainstorm‑ideas, identify‑assumptions, prioritize‑assumptions, brainstorm‑experiments) based on your request:

Run product discovery on "AI‑powered meeting summarizer": brainstorm ideas, map assumptions, prioritize the risky ones, then design experiments.

Create Reusable Custom Skills

For frequently used workflows, convert Claude command files into Codex-specific skills:

Read the command file for /discover in the pm‑execution plugin and create a Codex skill that performs the same steps.

This creates a reusable command-like skill within Codex, though some Claude-specific syntax may require manual adjustment during conversion.

Claude vs. Codex: Command Syntax Comparison

Understanding the syntax differences helps clarify the workflow translation:

In Claude (where slash commands work):

/discover AI‑powered meeting summarizer for remote teams

Equivalent in Codex (natural language):

Run product discovery on "AI‑powered meeting summarizer for remote teams": 
- brainstorm ideas 
- identify assumptions 
- prioritize the riskiest assumptions 
- design experiments.

Alternative in Codex (custom skill):

# Assuming you created a skill named 'discover'

codex run discover "AI‑powered meeting summarizer for remote teams"

Key Files Understanding the Architecture

These source files clarify why functionality differs between platforms:

• README.md (lines 82-86, 104-106): Documents the explicit limitation that slash commands install but do not execute in Codex
• pm-toolkit/commands/*.md (e.g., discover.md): Contains Claude-specific command definitions that Codex cannot expose as slash commands
• pm-toolkit/skills/*/SKILL.md (e.g., brainstorm-ideas-new/SKILL.md): Defines the reusable skill blocks accessible to both assistants
• CLAUDE.md: Describes marketplace structure and clarifies which components are Claude-only

Summary

• Slash commands are Claude-only: The /discover, /write-prd, and similar shortcuts only function in Claude Code or Claude Cowork
• Skills remain cross-platform: The underlying skill definitions in pm-toolkit/skills/ work identically in both Claude and Codex
• Natural language replaces slash syntax: Describe workflows in plain English to trigger the same skill chains
• Custom skills offer shortcuts: Convert command files to Codex skills for reusable shortcuts without slash syntax

Frequently Asked Questions

Can I modify PM Skills to make slash commands work in Codex?

No, this limitation stems from Codex's core plugin architecture, not from PM Skills configuration. Codex simply does not expose plugin functionality through slash commands, regardless of how the skills are packaged or modified. You must use natural language prompts or custom skills to access the functionality.

Will future versions of Codex CLI support slash commands?

The repository documentation does not indicate any upcoming changes to Codex's plugin exposure model. The current implementation treats Codex as a natural-language-first environment where plugins are invoked contextually rather than through explicit slash commands. Monitor the phuryn/pm-skills repository for updates to CLAUDE.md or README.md regarding platform parity.

Do I need to install different files for Codex versus Claude?

No, the installation uses the same marketplace and plugin files. The command codex plugin marketplace add phuryn/pm-skills pulls the identical source code that Claude uses. The difference lies entirely in how each platform exposes the installed functionality—Claude through slash commands, Codex through natural language skill invocation.

Are the underlying skills less powerful in Codex without slash commands?

No, the skills (brainstorm‑ideas, identify‑assumptions, prioritize‑assumptions, etc.) contain identical logic and capabilities in both environments. The slash commands in Claude merely provide a convenience wrapper that chains these skills together. In Codex, you achieve the same result by describing the chain in natural language, giving you potentially more flexibility in customizing the workflow steps.

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