A writing tool for a product requirements document (PRD), which explains what a product or feature needs to do, plus a companion document describing how success will be measured. It builds these documents from an approved product brief when available.

Use it to create or update product requirements, describe use cases and priorities, consider different product surfaces, and define business, adoption, activation, and retention measurements.

It turns an agreed product idea into a more detailed plan for design and engineering. It also provides a defined path when the brief is missing, including a short idea-gathering step.

How ertra/pm-brain-for-cursor configures Claude Code and Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to ertra/pm-brain-for-cursor. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ertra/pm-brain-for-cursor/main/.cursor/skills/create-prd/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ertra/pm-brain-for-cursor

Made for: Claude Code, Cursor.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ertra/pm-brain-for-cursor/create-prd/github.svg)](https://agentmods.dev/skills/ertra/pm-brain-for-cursor/create-prd)

Your own site

<a href="https://agentmods.dev/skills/ertra/pm-brain-for-cursor/create-prd"><img src="https://agentmods.dev/badge/skills/ertra/pm-brain-for-cursor/create-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ertra/pm-brain-for-cursor/create-prd"><img src="https://agentmods.dev/badge/skills/ertra/pm-brain-for-cursor/create-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,680 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.

Model	Per session	Once invoked
Fable 5.1	$0.00056	$0.03680
Opus 5.5	$0.00022	$0.01472
Sonnet 5.5	$0.00011	$0.00736
Haiku 4.5	$0.00006	$0.00368

Measured 1mo ago against content hash 974de8ead8f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-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 1mo 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.

.cursor/skills/create-prd/SKILL.md · 271 lines

How it starts

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

PRD Writer (pm-brain)

Write the PRD pack — product requirements and success metrics — ideally from an approved product brief (01-product-brief.md in the feature hub or an explicit brief path). Preferred: brief exists → skip Step 0.5 and use the brief as source of truth. If no brief: offer create-product-brief first; if the user wants a PRD anyway, run Step 0.5 (braindump gate per PRODUCT-RULES.md) before Step 1.

Repo convention: Feature hub paths, skipping steps, and the skills table — see 02-templates/README.md (Feature hub convention, Skipping steps, Cursor skills).

The pack is two tightly-coupled files:

02-product-requirements.md — use cases, priorities, cross-surface considerations
03-success-metrics.md — business impact, activation, adoption, retention, proposed new events

Step 0: Locate the product brief

Ask for the PROJECT Jira key (PROJECT-abcde) or the path to an existing product brief.
Resolve the feature-hub folder: projects/{PROJECT-KEY}-{slug}/.
- If only the key is given, list projects/ and match the PROJECT-{KEY}-* directory.
- If multiple match, show them and ask which one.
Confirm a brief is available:
- 01-product-brief.md in the feature hub, or
- An explicit brief path the user provided in Step 0. If neither exists, suggest create-product-brief or an external brief path. If they still want a PRD without a brief, continue to Step 0.5 (braindump gate).

Step 0.5: Braindump gate (only when no brief)

Run this step only if neither 01-product-brief.md in the feature hub nor an explicit external brief path is available. If either brief exists, skip Step 0.5 — the brief is the braindump; go to Step 1.

When no brief is available, follow PRODUCT-RULES.md before Step 1:

Ask 3–5 product-sense questions from PRODUCT-RULES.md.
Confirm the braindump sufficient? checklist (all four items — see PRODUCT-RULES.md).
If any item is missing, ask one more targeted question and wait.
Override: If the user says "skip braindump", proceed to Step 1 and log braindump: skipped by user in both PRD files' frontmatter when you write them.

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

1mo ago First seen · 271 lines · 56 tokens per session scan A 974de8ead8f3

Subscribe to this mod's changes

create-prd is a skill published in the GitHub repository ertra/pm-brain-for-cursor (22 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 3,680 once invoked, about $0.0002 per session on Opus 5.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-30.

Planning Writing and docs product productmanagement productmanager

replit-deck

For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query "pm-feature-business-case-deck", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident…

nexu-io/open-design · 71 tokens

pm-brain-for-cursor: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

PRD Writer (pm-brain)

Step 0: Locate the product brief

Step 0.5: Braindump gate (only when no brief)

What this file has done since we first saw it

Other skills, from other repositories

replit-deck

hps-true-blueprint

design-critique

analytics-product

deck-open-slide-canvas

mockup-device-3d