What is prd-generator?

A question-and-specification guide that creates a Product Requirements Document, a structured description of what a software feature should do. It saves the result as prd.json for the Ralph autonomous coding loop.

It helps plan features and projects, collect essential answers, write user stories and acceptance details, and prepare work for Ralph to implement.

It turns an idea into clear implementation requirements before coding begins, while exposing missing decisions about scope, users, technology, and success.

prd-generator — Skill for Claude Code and Codex by brenbuilds1

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 brenbuilds1/copilot-ralph --skill prd

Clone the repo

git clone --depth 1 https://github.com/brenbuilds1/copilot-ralph

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/brenbuilds1/copilot-ralph/prd/github.svg)](https://agentmods.dev/skills/brenbuilds1/copilot-ralph/prd)

Your own site

<a href="https://agentmods.dev/skills/brenbuilds1/copilot-ralph/prd"><img src="https://agentmods.dev/badge/skills/brenbuilds1/copilot-ralph/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/brenbuilds1/copilot-ralph/prd"><img src="https://agentmods.dev/badge/skills/brenbuilds1/copilot-ralph/prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,209 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.00069	$0.02209
Opus 5.5	$0.00028	$0.00884
Sonnet 5.5	$0.00014	$0.00442
Haiku 4.5	$0.00007	$0.00221

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

Security

Grade A, and why

prd-generator 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.

skills/prd/SKILL.md · 310 lines

How it starts

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

PRD Generator

Create detailed Product Requirements Documents that are clear, actionable, and suitable for autonomous implementation by Ralph.

The Job

Receive a feature description from the user
Ask 3-5 essential clarifying questions (with lettered options)
Generate a structured PRD based on answers
Save to prd.json in project root

Important: Do NOT start implementing. Just create the PRD.

Step 1: Clarifying Questions

Ask only critical questions where the initial prompt is ambiguous. Focus on:

Problem/Goal: What problem does this solve? Why build this?
Core Functionality: What are the key user actions?
Scope/Boundaries: What should it NOT do?
Technology: What stack/framework to use?
Success Criteria: How do we know it's done?

Format Questions Like This:

1. What is the primary goal of this feature?
   A. Improve user onboarding experience
   B. Increase user retention
   C. Reduce support burden
   D. Other: [please specify]

2. Who is the target user?
   A. New users only
   B. Existing users only
   C. All users
   D. Admin users only

3. What is the scope?
   A. Minimal viable version (MVP)
   B. Full-featured implementation
   C. Just the backend/API
   D. Just the UI/frontend

4. What technology stack?
   A. React + Node.js
   B. Next.js
   C. Plain HTML/CSS/JS
   D. Other: [please specify]

5. What's explicitly OUT of scope?
   A. Authentication/login
   B. Database persistence
   C. Mobile responsiveness
   D. None of the above - include everything

This lets users respond with "1A, 2C, 3A, 4B, 5A" for quick iteration.

Step 2: Break Down Into User Stories

After gathering answers, break the feature into small, focused user stories.

Story Size Rule

Each story must be small enough to complete in one Ralph iteration (one agent context window, ~15-30 minutes of focused work).

Good story sizes:

Add a single component
Create one API endpoint
Add form validation
Create a database migration
Wire up frontend to API

Read the full file on GitHub · 310 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.

1mo ago First seen · 310 lines · 69 tokens per session scan A 7305fe677f65

Subscribe to this mod's changes

prd-generator is a skill published in the GitHub repository brenbuilds1/copilot-ralph (50 stars, last pushed 9mo ago), licensed MIT. It adds 69 tokens to every session and 2,209 once invoked, about $0.0003 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.

Building agents Planning

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

systematic-debugging

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

obra/superpowers · 21 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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 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