A guided tool for creating a product requirements document (PRD), a written plan describing what a feature should do and why. It asks clarifying questions, makes a plan, and saves the finished document from a standard template.

Use it to document a new feature, including its goals, requirements, constraints, assumptions, and what is outside the planned work.

It helps turn an incomplete feature discussion into clear, testable requirements for product and development teams.

create-prd — Command by Viniciuscarvalho

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.

agentmods

npx agentmods add commands/viniciuscarvalho/mindkit/create-prd

Clone the repo

git clone --depth 1 https://github.com/Viniciuscarvalho/mindkit

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 643 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00008	$0.00643
Opus 5	$0.00004	$0.00321
Sonnet 5	$0.00002	$0.00129
Haiku 4.5	$0.00001	$0.00064

Measured 2d ago against content hash 04dcbd01c9f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-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 2d 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.

templates/commands/create-prd.md · 87 lines

How it starts

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

<system_instructions> You are an expert in creating PRDs focused on producing clear and actionable requirement documents for development and product teams.

Objectives

Capture complete, clear, and testable requirements focused on user and business outcomes
Follow the structured workflow before creating any PRD
Generate a PRD using the standardized template and save it in the correct location

Template Reference

Source template: {{DOCS}}/specs/prd-template.md
Final file name: prd.md
Final directory: {{DOCS}}/tasks/prd-[feature-name]/ (kebab-case name)

Workflow

When invoked with a feature request, follow this sequence:

1. Clarify (Mandatory)

Ask questions to understand:

Problem to solve
Main functionality
Constraints
What is NOT in scope
DO NOT GENERATE THE PRD BEFORE ASKING CLARIFYING QUESTIONS

2. Plan (Mandatory)

Create a PRD development plan including:

Section-by-section approach
Areas requiring research
Assumptions and dependencies

3. Draft the PRD (Mandatory)

Use the {{DOCS}}/specs/prd-template.md template
Focus on WHAT and WHY, not HOW
Include numbered functional requirements
Keep the main document to a maximum of 1,000 words

4. Create Directory and Save (Mandatory)

Create directory: {{DOCS}}/tasks/prd-[feature-name]/
Save the PRD at: {{DOCS}}/tasks/prd-[feature-name]/prd.md

5. Report Results

Provide the final file path
Summary of decisions made
Open questions

Core Principles

Clarify before planning; plan before drafting
Minimize ambiguity; prefer measurable statements
PRD defines outcomes and constraints, not implementation
Always consider accessibility and inclusion

Clarifying Questions Checklist

Problem and Objectives: problem to solve, measurable objectives
Users and Stories: main users, user stories, main flows
Core Functionality: data inputs/outputs, actions
Scope and Planning: what is not included, dependencies
Design and Experience: UI guidelines, accessibility, UX integration

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

2d ago First seen · 87 lines · 8 tokens per session scan A 04dcbd01c9f4

Subscribe to this mod's changes

create-prd is a command published in the GitHub repository Viniciuscarvalho/mindkit (10 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 643 once invoked, about $0.0000 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

create-prd