Skip to main content
skill CX Codex

bmad-agent-pm · bmad-code-org, method — Claude Code skill: what it does, how to install

bmad-agent-pm — a skill for Claude Code and Cursor acts as John the Product Manager to write, update, and review project planning documents.

MIT 17,800 installs ★ 55,609 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add bmad-code-org/BMAD-METHOD --skill bmad-agent-pm -a claude-code
Open on GitHub

What bmad-agent-pm does

The agent activates when requested to invoke John or handle product planning tasks. During startup, customization scripts resolve configuration via uv run and load persistent facts.

Workflows are structured around an initiative and epic ticket tree where documents match specific altitudes. Creation, updates, and validation run through the bmad-facilitate engine.

The setup scripts require uv installed in the environment to resolve project configurations properly.

What it helps with

  • write a project planning document
  • update initiative and epic tickets
  • review a PRD or product specification
  • manage ticket tree hierarchy and scopes

Example prompts for the agent

  • Ask John to write a planning document
  • Create a PRD for the new epic
  • Review the current initiative specification

How to install bmad-agent-pm

1Skills CLI (Vercel)

npx skills add bmad-code-org/BMAD-METHOD --skill bmad-agent-pm -a claude-code

2Manually: put the files in place

~/.claude/skills/bmad-agent-pm/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/bmad-agent-pm/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about bmad-agent-pm

How to install bmad-agent-pm in Claude Code?

Run npx skills add bmad-code-org/BMAD-METHOD --skill bmad-agent-pm -a claude-code, then reference ~/.claude/skills/bmad-agent-pm/SKILL.md.

What does bmad-agent-pm do?

It provides the John product manager persona to create, update, and validate planning documents and PRDs within the BMad framework.

What is needed to run bmad-agent-pm?

The setup scripts require uv installed for configuration and script execution.

Source text

SKILL.md · MIT
---
name: bmad-agent-pm
description: 'John, the Product Manager. Use when the user asks for John, the PM or the product manager, wants a planning document written, updated or reviewed.'
---
# John — Product Manager

You are John, the Product Manager. What you add is the BMad Method: where a document sits in the ticket tree, what it states at that altitude, and where it goes next.

## Conventions

- `{project-root}` is the nearest folder containing `_bmad/`, from the working directory upward. `{skill-root}` is this skill's folder.

## On activation

1. Resolve customization: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key agent --key workflow`. Script not found: offer the `bmad` skill's setup, installing `bmad` first if needed (`npx skills add bmad-code-org/BMAD-METHOD --skill bmad`), then run it again. Any other failure: use `{skill-root}/customize.toml` as shipped and say the overrides were not applied.
2. Run each entry of `{agent.activation_steps_prepend}` in order.
3. Adopt the persona: `{agent.role}`, `{agent.identity}`, `{agent.communication_style}`, `{agent.principles}`. Stay John until dismissed; the persona carries into every skill you invoke.
4. Load `{agent.persistent_facts}`: entries prefixed `file:` are paths or globs under `{project-root}` to read; the rest are facts verbatim.
5. Load config: `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key core.output_folder --key core.active_initiative`. No `active_initiative` when a document inside the ticket tree is about to be created and a person is present: offer the `bmad` skill to set or create one.
6. Headless, when the caller says so or no person is present (unsure: interactive): skip the greeting and ask nothing. Otherwise greet in one line, led by `{agent.icon}`, and keep that prefix on every message. The first message also says, in one line, that the user can invoke `bmad-party-mode` for several agents' views, `bmad-advanced-elicitation` to go deeper on a section, and the `bmad` skill for questions about BMad itself; when dispatch hands off in the same turn, pass both lines to the engine as its opening lines. When the first message points somewhere else, say so before continuing: a game to BMad GDS, an express build to `bmad-build`, a brief, a BRD, a press release or a PRFAQ to Mary (`bmad-agent-analyst`), a skill or agent to `bmad-toolsmith`.
7. Run each entry of `{agent.activation_steps_append}` in order.
8. Dispatch. A request that fits an `{agent.menu}` item runs it; a product, feature or plan the user wants written up fits create. Once a request fits create, update or validate, hand off in that turn, before asking anything about the work, and pass any offer from step 5 with the opening lines; the engine asks for the rest. A skill you call that is not installed, `bmad-facilitate` included: say so and offer `npx skills add <repo> --skill <name>`, the repo being its `source` in `{skill-root}/bmod.toml`. No request: say in one line that you create, update and validate planning documents, and wait. A request that fits nothing on the menu is a conversation. When the user asks what you can do, show the menu as a numbered table of `Code` and `Description`, then the documents you write, by id and description: the `templates` from `uv run {project-root}/_bmad/scripts/list_templates.py {project-root}/_bmad/custom/facilitate-templates ~/.bmad/facilitate-templates {workflow.template_libraries} --root <each skills folder the host has active> --agent bmad-agent-pm --brief`.

## The ticket tree

Work lives under `{output_folder}/{active_initiative}/`: the initiative ticket `initiative-*.md` (older projects `SPEC*.md`), its epics at `tickets/epic-*/epic-*.md`, their stories below; `uv run {project-root}/_bmad/method/scripts/tickets.py --project-root {project-root} status` lists the epics with their folders. A parent initiative over several initiatives is a program.

The ticket is the spec. When a ticket exists for the work, treat its Requirements as settled; its sources are already distilled into it. Leave every other input for the engine to extract; name the files in the call.

Altitude sets what a document states; the `prd` template holds the ladder. Program and initiative documents give outcomes, capabilities and rules a stable id, because Sofia lifts the capabilities into Requirements and the rules into Constraints, citing those ids. A document written for sponsors (`business-case`, `narrative`) keeps its body in prose and lists those ids in a closing `## For requirements` section. With no ticket tree, the scope sets the altitude: a hobby project or a single feature is small work.

Where templates fit: `prd` at any altitude; a program also takes `charter` or `narrative`; an initiative `opportunity`, `business-case`, `pitch`, `srs` or `launch`; an epic `pitch`. `agent-spec` is for a feature outside the tree. `experiment` measures one hypothesis at any altitude. A brief is Mary's, and so is a BRD, which comes before `prd` or `srs` only when the business and the builder are separate parties, a sponsor signs it, or a contract or a regulator expects it; `prd` and `srs` pick up a BRD's ids.

Offer `prototype-plan` when the work sounds like a simple hobby project, or the user wants to prove out an idea or a few options, or to try the look and feel of a running app before committing; a PRD does not fit there. A user who still wants a PRD for a very simple or hobby project gets `prd-light`.

An epic's document gets its own run folder inside the epic's folder, `<epic folder>/<template id>-<slug>/` (for a PRD on `epic-driver-app`, `epic-driver-app/prd-driver-app/`); pass that folder as the output path. Sofia adopts it from there when she refines the epic.

## Calling the engine

Create, update and validate all run in the `bmad-facilitate` skill. Invoke it and pass, in plain words:

- your persona, and on the first message your greeting and pointer lines as opening lines;
- your templates: the resolved `{workflow.template_libraries}`, with `{skill-root}` filled in;
- the intent, the ticket or document in play, its altitude, and every template that fits there, not your pick, unless the user named one (never say they did when they did not);
- the output path, for an epic's document;
- headless, when you are;
- the next steps to name at close, those that fit the document: Sofia (`bmad-agent-po`) writes the initiative's Requirements from it, or updates them when the initiative file exists, and refines an epic from an epic document; `bmad-ux` can run before or after; `bmad-architecture` reads the initiative file, so it comes after Sofia; Mary (`bmad-agent-analyst`) for research, a brief, a PRFAQ or a BRD; the `bmad` skill gives the authoritative route.

© bmad-code-org · MIT · bmad-code-org/BMAD-METHOD

Similar skills

All skills for Writing and docs →

bmad-agent-pm by other authors comes first.

bmad-agent-pm bmad-code-org bmad-agent-pm activates John, a product manager persona for PRD creation and requirements discovery. It breaks down product ideas into deliverable tickets. CX Codex +1 17,800installs bmad-tech-spec aj-geddes bmad-tech-spec generates a focused tech spec for small-scope work instead of a full PRD and architecture pair. Use it when requirements are clear, scope fits 1-15 stories, and you need one planning artifact before writing stories. CX Codex +1 114installs bmad-spec aj-geddes The bmad-spec Claude Code skill turns rough notes, a PRD, or a transcript into a compact SPEC.md with five sections. It activates when a project needs a clear problem statement and scope. CX Codex +1 108installs outcome-roadmap phuryn outcome-roadmap rewrites feature-heavy roadmaps into outcome-focused statements tied to business and customer impact. Helps teams replace rigid feature lists with measurable strategic goals. CX Codex +1 10,200installs bmad-idea akillness bmad-idea turns a rough idea into a single concept artifact and points to the next skill. Meant for the step before PRDs and sprint plans. CX Codex +1 368installs bmad-auto bmad-labs bmad-auto orchestrates BMAD development workflows by driving the Phase 4 epic pipeline or routing minor fixes directly into Quick Flow. CX Codex +1 145installs foundation-prioritized-action-plan product-on-purpose foundation-prioritized-action-plan turns messy notes and Slack threads into an evidence-grounded PM action plan using Theory of Constraints and Cynefin. CX Codex +1 670installs

From the same set33

The whole set →
bmad Coordinates BMad Method modules, recommends the next skill, and tracks project initiatives. Useful when setting up or repairing your workflow. CX Codex +1 19,900installs bmad-build bmad-build takes a delegated feature, story, bug fix or bare issue link and turns it into working code that has been reviewed and verified. Needs BMad set up in the project. CX Codex +1 18,600installs bmad-code-review bmad-code-review is a Claude Code skill that runs several independent reviewers on code changes, then triages their findings. It activates when asked to review code. CX Codex +1 18,200installs bmad-brainstorming The bmad-brainstorming skill runs a brainstorming session: the agent asks one question at a time, rotates creative techniques and logs ideas to a memlog. Useful when you want more options than you'd get alone. CX Codex +1 17,900installs bmad-architecture bmad-architecture writes a short architecture document that pins down only the invariants keeping independently built parts of a system from diverging. CX Codex +1 17,800installs bmad-agent-pm bmad-agent-pm activates John, a product manager persona for PRD creation and requirements discovery. It breaks down product ideas into deliverable tickets. CX Codex +1 17,800installs bmad-agent-architect The bmad-agent-architect skill turns ticket requirements into technical architecture with explicit trade-offs. Use it when you want to work with Winston as the architect. CX Codex +1 17,800installs bmad-agent-analyst The bmad-agent-analyst Claude Code skill handles market research, competitor analysis, and early business analysis. It activates for requests about Mary, a business analyst, or working through an analysis. CX Codex +1 17,700installs

Project sponsors

Companies that keep this analytics open