pm-prd

A product requirements document, or PRD, for defining one feature before it is built. It can follow Shape Up, a pitch-based planning method, or a standard PRD format.

In plain words
What is it for?
It helps teams describe the feature, intended users, effort limits, open questions, and things the work will not include.
Why use it?
It turns an idea into an agreed problem, scope, proposed solution, and list of risks or exclusions.

Skill for Claude CodeCodex

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-prd
Any agent
npx skills add nmrtn/nanopm --skill pm-prd
Clone the repo
git clone --depth 1 https://github.com/nmrtn/nanopm

Made for: Claude Code, Codex.

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,726 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.

ModelPer sessionOnce invoked
Fable 5 $0.00043 $0.07726
Opus 5 $0.00022 $0.03863
Sonnet 5 $0.00009 $0.01545
Haiku 4.5 $0.00004 $0.00773

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

Security

Grade C, and why

pm-prd 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 2d 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-prd/SKILL.md · 635 lines

How it starts

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

Multi-host portability rules. When invoking AskUserQuestion:

  1. 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.
  2. 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
_PRD_DIR=".nanopm/wiki/docs/prds"
mkdir -p "$_PRD_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-prd

If found: "Prior PRD found from {ts}. Starting a new PRD."

Phase 1: Identify the feature

1.0. Chosen-solution input (optional — purely additive)

First scan your launch context / arguments for a chosen-solution hint — the way the user invoked the skill. Two equivalent forms, matching how nanopm skills parse structured hints:

  • /pm-prd <solution-slug> — a bare argument that is a kebab slug naming a file under .nanopm/wiki/entities/solutions/.
  • /pm-prd --chosen <solution-slug> — the explicit form.

Resolve the slug to _SOLUTION_SLUG only if .nanopm/wiki/entities/solutions/<slug>.md exists:

[ -n "$_SOLUTION_SLUG" ] && [ -f ".nanopm/wiki/entities/solutions/${_SOLUTION_SLUG}.md" ] \
  && echo "SOLUTION_FOUND: $_SOLUTION_SLUG" || echo "SOLUTION_NONE"
  • SOLUTION_NONE (no hint, or the slug names no real file) → clear _SOLUTION_SLUG and run the rest of the skill exactly as before — the chosen-solution path is purely additive and never changes the no-argument behaviour. If a slug was passed but matched no file, say so once ("No solution <slug> under .nanopm/wiki/entities/solutions/ — writing a PRD from scratch.") and fall through to the normal flow.
  • SOLUTION_FOUND → run 1.1 (seed from the chosen solution) below instead of the feature-prompt that follows, then continue to Phase 2 with the seeded _FEATURE and seed notes.

Read the full file on GitHub · 635 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. 2d ago First seen · 635 lines · 43 tokens per session scan C 5ba038072058

Subscribe to this mod's changes

pm-prd is a skill published in the GitHub repository nmrtn/nanopm (48 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 7,726 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

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

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

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 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