A product-requirements document (PRD) writing rule for the /prd command. It turns product details, goals, risks, and user flows into a short plan for what to build.

Use it to create or update docs/PRD.md with scope, requirements, stakeholders, timelines, assumptions, risks, and measurable success criteria.

It removes the need to organise these details by hand and helps expose missing information before work starts. It can also use an existing design brief as source material.

02-prd — Cursor rule for Cursor by luiscielak/ai-product-design-rules

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.

Clone the repo

git clone --depth 1 https://github.com/luiscielak/ai-product-design-rules

Made for: 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/rules/luiscielak/ai-product-design-rules/02-prd/github.svg)](https://agentmods.dev/rules/luiscielak/ai-product-design-rules/02-prd)

Your own site

<a href="https://agentmods.dev/rules/luiscielak/ai-product-design-rules/02-prd"><img src="https://agentmods.dev/badge/rules/luiscielak/ai-product-design-rules/02-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/rules/luiscielak/ai-product-design-rules/02-prd"><img src="https://agentmods.dev/badge/rules/luiscielak/ai-product-design-rules/02-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 636 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.00035	$0.00636
Opus 5.5	$0.00014	$0.00254
Sonnet 5.5	$0.00007	$0.00127
Haiku 4.5	$0.00003	$0.00064

Measured 5d ago against content hash e4558b26d0bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

02-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 5d 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/rules/02-prd.mdc · 44 lines

What it actually says

Product Owner → Generate PRD

Command: /prd or /prd using docs/design-brief.md
Role: Product Owner
Purpose: Create a concise, actionable PRD to align scope, requirements, and metrics.
Prerequisites: Project structure should exist (run /new-project first if needed)
Required Inputs:
- product_name, target_users, key_problem, business_goals, success_metrics
- primary_flows (list), constraints, assumptions, risks, stakeholders, timeline
- Optional: Reference to existing design brief (e.g., "using docs/design-brief.md" or "from design-brief.md")
Behavior:
- If design brief is referenced: Read the design brief file first and extract relevant information to populate PRD sections
- If no design brief: Validate inputs; ask for missing critical info only once, then proceed with best assumptions
- Keep PRD short but complete; prefer bullet points and measurable criteria
- Automatically search for and reference existing design briefs in docs/ directory if not explicitly provided
- If project_name not provided, infer from current directory or ask once
- Note: When working within a project directory (projects/{project_name}/), use relative paths (e.g., docs/PRD.md)
Output:
- File: docs/PRD.md (relative to project directory)
- Format:
  1. Overview: product_name, elevator_pitch, problem_statement
  2. Goals and Non-Goals
  3. Target Users and Personas
  4. User Stories (INVEST format) and Primary Flows
  5. Scope (MVP vs. Post-MVP)
  6. Functional Requirements (numbered FR-001, FR-002…)
  7. Non-Functional Requirements (NFR-001, NFR-002…: performance, security, accessibility)
  8. Acceptance Criteria (Gherkin-style where useful: Given/When/Then)
  9. Success Metrics (north star + leading indicators; baselines and targets)
  10. Dependencies and Constraints
  11. Assumptions and Open Questions
  12. Risks and Mitigations
  13. Release Plan and Milestones
Acceptance:
- All FRs map to at least one user story and metric
- Each metric has a target, timeframe, and measurement method
- PRD is actionable and scoped appropriately for MVP
- File is saved to correct location and properly formatted

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.

5d ago First seen · 44 lines · 35 tokens per session scan A e4558b26d0bc

Subscribe to this mod's changes

02-prd is a cursor rule published in the GitHub repository luiscielak/ai-product-design-rules (4 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 636 once invoked, about $0.0001 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-10-28.

Planning Project management

slice-tasks

PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.

danielvm-git/bigpowers · 59 tokens

iris

GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.

ils15/pantheon-legacy · 43 tokens

elite-orchestrator

Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…

MN-Lizard-Team/aiyu-multi-agent · 94 tokens

02-prd