create-prp

A guided writer for a Product Requirement Prompt, a detailed document that explains what a feature or product should do and how to build it. It uses project documentation, templates, and outside research as context.

In plain words
What is it for?
Use it to research a feature, review relevant files and templates, and produce a comprehensive PRP for another coding agent to implement.
Why use it?
It helps turn a rough feature idea into a structured implementation brief and exposes missing documentation before development begins.

Command for Claude Code

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/wirasm/dylan/create-prp
Clone the repo
git clone --depth 1 https://github.com/Wirasm/dylan

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 572 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00572
Opus 5 $0.00000 $0.00286
Sonnet 5 $0.00000 $0.00114
Haiku 4.5 $0.00000 $0.00057

Measured yesterday against content hash 069ce58b41ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-prp 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 yesterday.

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/commands/create-prp.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 MUST READ THESE FILES AND FOLLOW THE INSTRUCTIONS IN THEM. Start by reading the concept_library/cc_PRP_flow/README.md to understand what a PRP Then read concept_library/cc_PRP_flow/PRPs/base_template_v1 to understand the structure of a PRP.

Think hard about the concept

Help the user create a comprehensive Product Requirement Prompt (PRP) for: $ARGUMENTS

Instructions for PRP Creation

Research and develop a complete PRP based on the feature/product description above. Follow these guidelines:

Research Process

Begin with thorough research to gather all necessary context:

  1. Documentation Review

    • Check for relevant documentation in the ai_docs/ directory
    • Identify any documentation gaps that need to be addressed
    • Ask the user if additional documentation should be referenced
  2. WEB RESEARCH

    • Use web search to gather additional context
    • Research the concept of the feature/product
    • Look into library documentation
    • Look into example implementations on StackOverflow
    • Look into example implementations on GitHub
    • etc...
    • Ask the user if additional web search should be referenced
  3. Template Analysis

    • Use concept_library/cc_PRP_flow/PRPs/base_template_v1 as the structural reference
    • Ensure understanding of the template requirements before proceeding
    • Review past templates in the PRPs/ directory for inspiration if there are any
  4. Codebase Exploration

    • Identify relevant files and directories that provide implementation context
    • Ask the user about specific areas of the codebase to focus on
    • Look for patterns that should be followed in the implementation
  5. Implementation Requirements

    • Confirm implementation details with the user
    • Ask about specific patterns or existing features to mirror
    • Inquire about external dependencies or libraries to consider

PRP Development

Create a PRP following the template in concept_library/cc_PRP_flow/PRPs/base_template_v1, ensuring it includes the same structure as the template.

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. yesterday First seen · 77 lines · 0 tokens per session scan A 069ce58b41ce

Subscribe to this mod's changes

create-prp is a command published in the GitHub repository Wirasm/dylan (37 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 572 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-31.