What is apdr-prd-writer?

A product requirements document (PRD) writer that turns approved requirements into a structured plan for a feature or product.

It helps define MoSCoW priorities (must, should, could, or will not), user stories, Given/When/Then acceptance criteria, data contracts, release targets, and success measures.

It keeps product decisions, priorities, user needs, checks for completion, data rules, and dependencies in one place.

apdr-prd-writer — Skill for Claude Code and Codex by lazysheep-z

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 lazysheep-z/apdr-product-design-runtime --skill prd-writer

Clone the repo

git clone --depth 1 https://github.com/lazysheep-z/apdr-product-design-runtime

Made for: Claude Code, Codex.

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/lazysheep-z/apdr-product-design-runtime/prd-writer/github.svg)](https://agentmods.dev/skills/lazysheep-z/apdr-product-design-runtime/prd-writer)

Your own site

<a href="https://agentmods.dev/skills/lazysheep-z/apdr-product-design-runtime/prd-writer"><img src="https://agentmods.dev/badge/skills/lazysheep-z/apdr-product-design-runtime/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lazysheep-z/apdr-product-design-runtime/prd-writer"><img src="https://agentmods.dev/badge/skills/lazysheep-z/apdr-product-design-runtime/prd-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 557 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.00034	$0.00557
Opus 5	$0.00017	$0.00279
Sonnet 5	$0.00007	$0.00111
Haiku 4.5	$0.00003	$0.00056

Measured 11d ago against content hash 907de904ad5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

apdr-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 11d 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.

skills/prd-writer/SKILL.md · 54 lines

What it actually says

Product Writer (APDR)

Stage: prd. Requires RequirementsAnalysis status approved.

External skills (optional)

baoyu-format-markdown — polish exported PRD markdown
baoyu-slide-deck — /baoyu-slide-deck <prd.md> --outline-only --lang zh for stakeholder deck outline
pm-skills:strategy — /strategy (if pm-skills installed). Apply opportunity-solution tree or prioritization frameworks.

Workflow

get_latest_artifact — RequirementsAnalysis
If pm-skills available: invoke /strategy for strategic alignment before writing PRD.
For each requirement, define:

a) Feature definition
- id, name, description
- Priority: MoSCoW (must / should / could / wont)
- Dependencies on other features
- Target release / milestone
b) User stories
- "As a [persona], I want to [goal], so that [reason]"
- At least one story per persona per feature
c) Acceptance criteria
- Given/When/Then format
- Happy path + error path criteria
- Edge cases and boundary conditions
d) Data contracts (if applicable)
- Input fields expected, output fields returned
- Data types, formats, validation rules
- Reference: trpc/trpc 40k★ for API contract patterns
Define success metrics: how to measure each feature's impact
write_artifact — PRD with features, userStories, acceptanceCriteria, successMetrics
Status review → human approve_artifact before user flows
(Optional) Export PRD content to projects/{projectId}/exports/prd.md and run slide-deck outline

Do not

Treat slide-deck images as approved PRD — JSON artifact remains canonical
Let pm-skills strategy output replace the PRD artifact — incorporate insights but keep PRD JSON as canonical
Write acceptance criteria without covering both happy and error paths

References

phuryn/pm-skills 19k★ — prioritization frameworks
trpc/trpc 40k★ — API contract patterns

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.

11d ago First seen · 54 lines · 34 tokens per session scan A 907de904ad5a

Subscribe to this mod's changes

apdr-prd-writer is a skill published in the GitHub repository lazysheep-z/apdr-product-design-runtime (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 557 once invoked, about $0.0002 per session on Opus 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.

Planning Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens