What is pm-breakdown?

A planning tool that turns a product requirements document, or PRD, into engineering tasks and sends them to a chosen task-management format or system.

Use it to decompose a PRD for Linear, GitHub Issues, OpenSpec, gstack, Symphony, or readable Markdown task lists.

It removes the manual work of breaking a feature plan into actionable work and supports several destinations instead of assuming one project tool.

pm-breakdown — Skill by nmrtn

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.

agentmods

npx agentmods add skills/nmrtn/nanopm/pm-breakdown

Any agent

npx skills add nmrtn/nanopm --skill pm-breakdown

Clone the repo

git clone --depth 1 https://github.com/nmrtn/nanopm

Made for: Claude Code, Codex.

Or install nanopm, the plugin that ships this one along with the rest of its 26 skills, 1 hook.

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 8,879 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00055	$0.08879
Opus 5	$0.00028	$0.04439
Sonnet 5	$0.00011	$0.01776
Haiku 4.5	$0.00006	$0.00888

Measured 3d ago against content hash ed05c967b234, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

pm-breakdown scanned grade C with 2 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 3d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

{ echo "ERROR: nanopm not installed. Run: curl -fsSL https://raw.githubusercontent.com/nmrtn/nanopm/main/setup | bash"; exit 1; }

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

{ echo "ERROR: nanopm not installed. Run: curl -fsSL https://raw.githubusercontent.com/nmrtn/nanopm/main/setup | bash"; exit 1; }

pm-breakdown/SKILL.md · 831 lines

How it starts

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

Multi-host portability rules. When invoking AskUserQuestion:

The header field MUST be a short noun phrase (≤ 12 characters). Mistral Vibe rejects longer headers with string_too_long. Pick from: Start, Target, Scope, Audience, Methodology, Feature, Question.

The options list MUST have at least 2 items. Vibe rejects empty/single-option calls. For free-text input, always provide ≥ 2 framing options (e.g. Yes, here's the input / Skip) — never call ask_user_question with options: [].

Preamble (run first)

source ~/.nanopm/lib/nanopm.sh 2>/dev/null || \
  source .nanopm/lib/nanopm.sh 2>/dev/null || \
  { echo "ERROR: nanopm not installed. Run: curl -fsSL https://raw.githubusercontent.com/nmrtn/nanopm/main/setup | bash"; exit 1; }
nanopm_preamble
_TASKS_DIR=".nanopm/wiki/docs/tasks"
mkdir -p "$_TASKS_DIR"
_METHODOLOGY=$(nanopm_config_get "methodology")
echo "METHODOLOGY: ${_METHODOLOGY:-not set}"

Phase 0: Prior context

source ~/.nanopm/lib/nanopm.sh 2>/dev/null || source .nanopm/lib/nanopm.sh 2>/dev/null || true
nanopm_context_read pm-breakdown
nanopm_context_read pm-breakdown

Phase 1: Identify the PRD

ls .nanopm/wiki/docs/prds/*.md 2>/dev/null || echo "NO_PRDS"

If NO_PRDS: "No PRDs found in .nanopm/wiki/docs/prds/. Run /pm-prd first to create one." Exit.

If one PRD exists: use it automatically, tell the user: "Using PRD: {filename}"

If multiple PRDs exist: ask via AskUserQuestion which one. Store path as _PRD_FILE.

Phase 2: Read the PRD

Read _PRD_FILE. Extract:

Feature name
Problem statement
Functional requirements (numbered list)
Out of scope items
Ties to (objective/KR)
For Shape Up pitches: appetite, solution sketch, rabbit holes, no-gos

Derive the feature slug from the PRD filename: lowercase, hyphens, max 40 chars. Store as _FEATURE_SLUG.

With _FEATURE_SLUG and the PRD read, search for related opportunities and existing solutions — so tasks are grounded in the opportunity they serve and avoid duplicating prior work.

Read the full file on GitHub · 831 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.

3d ago First seen · 831 lines · 55 tokens per session scan C ed05c967b234

Subscribe to this mod's changes

pm-breakdown is a skill published in the GitHub repository nmrtn/nanopm (48 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 8,879 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning Project management

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

pm-breakdown