pm-workflow-problem-to-prd

pm-workflow-problem-to-prd is a skill for Claude Code from marfoerst/the-pragmatic-pm. It costs 124 tokens per session (2,376 once invoked), scanned A, original, MIT.

A staged workflow that turns a rough problem statement into a reviewed product requirements document (PRD), which explains what to build and why. It moves through customer jobs, personas, opportunities, feature details, and a final quality check.

In plain words
What is it for?
Use it to extract customer needs, describe target users, map solution opportunities, write feature requirements, and review the finished PRD.
Why use it?
It gives teams a clear path from an unclear problem to a checked specification. Each stage produces work that the next stage can use, reducing gaps between the original problem and the proposed product.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pm-toolkit plugin — 54 skills, 5 agents, 4 hooks shipped together

Good fit Use it to extract customer needs, describe target users, map solution opportunities, write feature requirements, and review the finished PRD.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/marfoerst/the-pragmatic-pm/pm-workflow-problem-to-prd
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add marfoerst/the-pragmatic-pm --skill pm-workflow-problem-to-prd
Clone the repo
git clone --depth 1 https://github.com/marfoerst/the-pragmatic-pm

Made for: Claude Code.

Or install pm-toolkit, the plugin that ships this one along with the rest of its 54 skills, 5 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pm-workflow-problem-to-prd

README.md
[![agentmods](https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-workflow-problem-to-prd/github.svg)](https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-workflow-problem-to-prd)
Your own site
<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-workflow-problem-to-prd"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-workflow-problem-to-prd/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pm-workflow-problem-to-prd

Your own site · 80×15
<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-workflow-problem-to-prd"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-workflow-problem-to-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,376 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00124 $0.02376
Opus 5 $0.00062 $0.01188
Sonnet 5 $0.00025 $0.00475
Haiku 4.5 $0.00012 $0.00238

Measured 11d ago against content hash b2662cf874c0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

pm-workflow-problem-to-prd scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/pm-workflow-problem-to-prd/SKILL.md · 281 lines

How it starts

The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow: Problem to PRD

You are a workflow orchestrator that takes a raw problem statement and produces a complete, reviewed PRD through a structured multi-stage chain. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context. Adapt all outputs to match that context. Also read personal-context.md if available to adapt guidance depth to the user's seniority and experience level. You help PMs go from fuzzy problem to shipping-ready spec.

Core Principles

  • Sequential with checkpoints: Each stage builds on the previous. Stop between stages for validation.
  • Working backwards: Start from the customer problem, not from the solution.
  • Artifact-driven: Each stage produces a named artifact that feeds the next stage.
  • Quality-gated: The final stage is a review — never ship an unreviewed PRD.

Workflow Overview

STAGE 1          STAGE 2           STAGE 3            STAGE 4         STAGE 5
JTBD          -> Persona        -> Opportunity     -> PRD          -> Review
Extract jobs     Define who        Map solution       Write the       Quality
& outcomes       we're solving     space              spec            check
                 for
[Artifact 1]     [Artifact 2]      [Artifact 3]       [Artifact 4]    [Artifact 5]
Job statements   Target persona    Opportunity tree    Complete PRD    Review report

Estimated time: 45-90 minutes (interactive, with pauses between stages)


Getting Started

Mid-Entry Support

Already have some of the inputs? Skip ahead:

If you already have... Skip to
Nothing — starting from scratch Stage 1 (start here)
JTBD / job statements Stage 2 (Persona Generation) — paste your job statements, I'll use them as Artifact 1
JTBD + Persona Stage 3 (Opportunity Tree) — paste both, I'll use them as Artifacts 1-2
JTBD + Persona + Opportunity analysis Stage 4 (PRD Generation) — paste all three, I'll generate the PRD directly
A draft PRD that needs review Stage 5 (Quality Review) — paste the PRD, I'll review it

Read the full file on GitHub · 281 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 281 lines · 124 tokens per session scan A b2662cf874c0

Subscribe to this mod's changes

pm-workflow-problem-to-prd is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 124 tokens to every session and 2,376 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.