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.
npx agentmods add skills/aakashg/pm-claude-code-setup/prd-writernpx skills add aakashg/pm-claude-code-setup --skill prd-writergit clone --depth 1 https://github.com/aakashg/pm-claude-code-setupWrote 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.
[](https://agentmods.dev/skills/aakashg/pm-claude-code-setup/prd-writer)<a href="https://agentmods.dev/skills/aakashg/pm-claude-code-setup/prd-writer"><img src="https://agentmods.dev/badge/skills/aakashg/pm-claude-code-setup/prd-writer.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.02918 |
| Opus 5 | $0.00000 | $0.01459 |
| Sonnet 5 | $0.00000 | $0.00584 |
| Haiku 4.5 | $0.00000 | $0.00292 |
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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- prd — 92% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRD Writer
Trigger
Activate on "write a PRD", "create a PRD", "draft a PRD", "PRD for [feature]", "spec out [feature]", or "one pager for [feature]".
Context
The PRD isn't dead. The bad PRD is dead. AI killed the 10-page PRD — no one read those. The modern PRD is lighter, sharper, and example-heavy.
Core philosophy:
- Think crisp, not complete. Teammates hate AI-generated bloat and crave human-written clarity. 2-3 pages max.
- PRDs are for alignment, not dictation. They drive discussion and decisions. They're what you discuss, debate, refer to, and sync on.
- A PRD engineers actually want to read nails the "why" and the "what," not the "how."
- You don't write a PRD once. You write it over time. The PRD is a living document reflecting the team's current thinking at each stage.
Behavior
Step 1: Clarify Before Writing
Before generating anything, ask 3-5 clarifying questions. Tailor to what's missing. Common gaps:
- Who specifically has this problem? (Not "users" — which users? Job title, company size, situation)
- What data do we have that this is worth solving? (Usage data, support tickets, revenue impact, customer quotes)
- What's the scope? (MVP vs full vision — and what stage is this PRD at?)
- Are there technical constraints the engineering team has flagged?
- What's the timeline and why?
Do NOT proceed until the user answers. A PRD without clear answers to these is vague and useless.
If the user is early-stage or exploring, generate a "speclet" (Stage 1) — just enough for the team to explore further. Never force a full PRD on an idea that needs discovery first.
Step 2: Determine the PRD Stage
The PRD evolves through stages. Ask or infer which stage the user is at:
| Stage | What It Is | What the PRD Looks Like |
|---|---|---|
| 1. Team Kickoff | Exploring the problem with design + eng | A "speclet" — title, problem hypothesis, 2-3 open questions. Maybe just a paragraph. |
| 2. Planning Review | Presenting to leadership for prioritization | A 1-pager: problem, strategic fit, initial data, potential approach. Audience: VP, CEO. |
| 3. XFN Kickoff | Bringing in sales, support, marketing, legal, QA | Expanded doc with cross-functional input needed. Compelling problem + initial solution direction. |
| 4. Solution Review | Staking a position on the solution | Full PRD with solution details, flows, edge cases. May be presented to senior leadership. |
| 5. Launch Readiness | Engineering handoff | Concrete specs: edge cases, metrics, user flows. Engineers comment heavily on this version. |
| 6. Impact Review | Post-launch learning | Add results link at top. What worked, what didn't, rollback notes. Closes the build-test-learn loop. |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 261 lines · 0 tokens per session scan A da055e0f1fac
prd-writer is a skill published in the GitHub repository aakashg/pm-claude-code-setup (152 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,918 tokens. 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.
Other skills, from other repositories
kimchi
Turn a raw product idea into build-ready docs — one doc per EPIC with locked decisions, exact API contracts, a story-by-story priority plan, and an execute.md handoff Claude can build from across sessions. Gets the clarity by interrogating the user through a roster of expert personas that grill, counter, and refuse to…
create-slide-deck
Create beautiful HTML slide decks for product presentations. Reads product context, extracts brand colors from websites, and generates self-contained HTML files with keyboard navigation and print-friendly layouts.
pm-setup
Interactive onboarding wizard that creates the PM-OS knowledge base for your product. Asks questions, fetches company info, and populates all knowledge files.
opportunity-assessment
Validate ideas with market sizing (TAM/SAM/SOM), competitive landscape, strategic alignment, technical feasibility, and a go/no-go recommendation.
pm-os
Product Manager's Operating System: gateway skill that routes requests to 27 PM workflow skills and manages the knowledge system.
competitive-intel
Research a competitor from their URL or name. Fetch website, pricing, features, and news. Generate a battlecard with positioning, strengths, weaknesses, and strategic implications.