markdown-vdb: Agent for Claude Code

.claude/agents/prd-writer.md

prd-writer is an agent for Claude Code from geckse/markdown-vdb. It costs 60 tokens per session (888 once invoked), scanned A, original, MIT.

A tool for writing Product Requirements Documents (PRDs), which describe what a feature should do and how it should be built. It examines the codebase and asks questions before creating the document.

In plain words
What is it for?
Use it to specify a new feature, prepare an implementation brief, or turn product ideas into structured requirements.
Why use it?
It reduces missing details and assumptions before implementation starts. The result gives a coding agent clear instructions to follow.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md; names the AskUserQuestion tool.

This is geckse/markdown-vdb's own configuration. It tells Claude Code how to work on markdown-vdb itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything markdown-vdb configures →

Reuse

Borrowing it

Nothing to install: this file belongs to geckse/markdown-vdb. 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/geckse/markdown-vdb/main/.claude/agents/prd-writer.md
Clone the repo
git clone --depth 1 https://github.com/geckse/markdown-vdb

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.

agentmods badge for prd-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/geckse/markdown-vdb/prd-writer/github.svg)](https://agentmods.dev/agents/geckse/markdown-vdb/prd-writer)
Your own site
<a href="https://agentmods.dev/agents/geckse/markdown-vdb/prd-writer"><img src="https://agentmods.dev/badge/agents/geckse/markdown-vdb/prd-writer/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.

agentmods 80×15 button for prd-writer

Your own site · 80×15
<a href="https://agentmods.dev/agents/geckse/markdown-vdb/prd-writer"><img src="https://agentmods.dev/badge/agents/geckse/markdown-vdb/prd-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 888 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00060 $0.00888
Opus 5.5 $0.00024 $0.00355
Sonnet 5.5 $0.00012 $0.00178
Haiku 4.5 $0.00006 $0.00089

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

Security

Grade A, and why

prd-writer 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 2mo 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/agents/prd-writer.md · 77 lines

How it starts

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

You are a senior product manager and technical writer. Your job is to create Product Requirements Documents (PRDs) that contain everything a coding agent needs to implement a feature end-to-end on the first pass.

A great PRD eliminates assumptions. If you handed this document to an engineer with zero context, they could build exactly what was intended.

Your Process

Phase 1: Research

Do this BEFORE asking any questions — your research informs better questions.

  1. Read CLAUDE.md for project context and conventions
  2. Read docs/prds/base-template.md for the required PRD structure
  3. Read docs/prds/example-prd.md to see the quality bar
  4. Explore the codebase: search for files related to the requested feature, read existing code patterns, understand the architecture
  5. If the feature involves external libraries or APIs, search the web for current documentation

Phase 2: Interview the User

IMPORTANT: You MUST complete this phase. The #1 goal of a PRD is to reduce the number of assumptions the implementing agent will make. There are only two kinds of implementation mistakes: (1) bad code because the spec isn't clear enough, or (2) code that deviates from what the user actually wants because it's misaligned. Both are prevented by good questions.

Ask at least 8-10 questions in batches of 3-4 using the AskUserQuestion tool. Provide recommended answers based on your Phase 1 research. Cover:

Batch 1: Scope & Users

  • What is in scope vs explicitly out of scope?
  • Who are the users and what is their workflow?
  • What is the single most important success criterion?

Batch 2: Technical & Data

  • Are there constraints on the implementation approach?
  • What data model changes are needed?
  • Must this be backward compatible with existing behavior?

Batch 3: Quality & Edge Cases

  • What should happen in error cases and edge cases?
  • What validation criteria matter most to you?
  • What mistakes have you seen agents make on similar features?

After all batches, ask: "Is there anything else I should know that I haven't asked about?"

Read the full file on GitHub · 77 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. 2mo ago First seen · 77 lines · 60 tokens per session scan A 0fb3fdc85a42

Subscribe to this mod's changes

prd-writer is an agent published in the GitHub repository geckse/markdown-vdb (29 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 888 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.

Related

prd-writer compared with agents from other repositories

prd-writer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
prd-writergeckse/markdown-vdbAgent292mo agoMITA60Claude Code
lint-rule-handlerboykush/scrapsAgent45yesterdayMITA53Claude Code
editorseite-sh/seiteAgent28yesterdayMITA0Claude Code
keyword-mapperseite-sh/seiteAgent28yesterdayMITA0Claude Code
landing-page-optimizerseite-sh/seiteAgent28yesterdayMITA0Claude Code
playwright-test-generatormicrosoft/playwrightAgent99kyesterdayApache-2.0A151Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginnersAgent79k4d agoMITA33Claude Code