A product requirements document, or PRD, that turns a validated product idea into an agreed plan for development. It covers goals, target users, user stories, acceptance criteria, exclusions, and measures of success.

Use it to create or review the product plan after idea validation, define user needs and success measures, and approve the requirements before development.

It gives the engineering team a shared description of what to build and how to judge whether it works. It also makes out-of-scope work explicit.

write-prd — Skill for Claude Code by evgenii-studitskikh

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 evgenii-studitskikh/Claude-Code-SaaS-Studio --skill write-prd

Clone the repo

git clone --depth 1 https://github.com/evgenii-studitskikh/Claude-Code-SaaS-Studio

Made for: Claude Code.

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/evgenii-studitskikh/claude-code-saas-studio/write-prd/github.svg)](https://agentmods.dev/skills/evgenii-studitskikh/claude-code-saas-studio/write-prd)

Your own site

<a href="https://agentmods.dev/skills/evgenii-studitskikh/claude-code-saas-studio/write-prd"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/write-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/evgenii-studitskikh/claude-code-saas-studio/write-prd"><img src="https://agentmods.dev/badge/skills/evgenii-studitskikh/claude-code-saas-studio/write-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 499 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.00044	$0.00499
Opus 5.5	$0.00018	$0.00200
Sonnet 5.5	$0.00009	$0.00100
Haiku 4.5	$0.00004	$0.00050

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

Security

Grade A, and why

write-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.

.claude/skills/write-prd/SKILL.md · 23 lines

What it actually says

Transform the idea-validation canvas into a structured Product Requirements Document that the engineering team can act on. Non-autonomous: every section is presented for approval before the file is written; review intensity controls how much detail is required before proceeding.

Phases

Load context — read docs/specs/idea-validation.md. If it is missing or contains a PIVOT/KILL verdict, stop and direct the user to /validate-idea first. Summarize the validated bet in two sentences and confirm it is still accurate.
Elicit goals and users — work through the PRD skeleton from .claude/templates/prd.md: confirm the primary goal, secondary goals, and the one or two target user personas. Ask one question at a time; do not over-interview.
Draft user stories — propose a ranked list of user stories in "As a [persona], I want [action] so that [outcome]" format, each with two or three acceptance criteria. Present the list; let the user add, remove, or reprioritize before proceeding.
Define non-goals and success metrics — propose explicit non-goals (what will NOT be built in v1) and two to four measurable success metrics tied to the goals. Get the user's sign-off on this list — it becomes the scope boundary for /scope-check.
Write the draft — fill .claude/templates/prd.md with everything gathered and write the draft to docs/specs/prd.md. Show the draft inline before writing; under full review, walk through each section; under lean or solo, write directly after a single confirmation.
Next step — on approval, point to /map-flows to derive the screen and journey list.

Output

docs/specs/prd.md — a complete PRD. Writes nothing else without approval.

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 · 23 lines · 44 tokens per session scan A 506a001ee18e

Subscribe to this mod's changes

write-prd is a skill published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (2 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 499 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-31.

Claude Code Planning Writing and docs agentic-workflows ai-agents claude-code-agents full-stack-development saas-development

agenticx-query-data-source

Use when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come from a live data source rather than training memory.

DemonDamon/AgenticX · 49 tokens

create-modal

Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, Select, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.

marcus/sidecar · 71 tokens

merge-strategy

Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…

marcus/sidecar · 63 tokens

write-prd