Borrowing it
Nothing to install: this file belongs to plipowczan/claude-piv-skeleton. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/plipowczan/claude-piv-skeleton/main/.claude/commands/product/create-prd.mdgit clone --depth 1 https://github.com/plipowczan/claude-piv-skeletonWrote 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/commands/plipowczan/claude-piv-skeleton/create-prd)<a href="https://agentmods.dev/commands/plipowczan/claude-piv-skeleton/create-prd"><img src="https://agentmods.dev/badge/commands/plipowczan/claude-piv-skeleton/create-prd.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.00007 | $0.01013 |
| Opus 5 | $0.00003 | $0.00507 |
| Sonnet 5 | $0.00001 | $0.00203 |
| Haiku 4.5 | $0.00001 | $0.00101 |
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 8d 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.
This is a copy
98% identical to create-prd — 29 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create PRD: Generate Product Requirements Document
Overview
Generate a comprehensive Product Requirements Document (PRD) based on the current conversation context and requirements discussed. Use the structure and sections defined below to create a thorough, professional PRD.
Output File
Write the PRD to: $ARGUMENTS (default: PRD.md)
PRD Structure
Create a well-structured PRD with the following sections. Adapt depth and detail based on available information:
Required Sections
1. Executive Summary
- Concise product overview (2-3 paragraphs)
- Core value proposition
- MVP goal statement
2. Mission
- Product mission statement
- Core principles (3-5 key principles)
3. Target Users
- Primary user personas
- Technical comfort level
- Key user needs and pain points
4. MVP Scope
- In Scope: Core functionality for MVP (use ✅ checkboxes)
- Out of Scope: Features deferred to future phases (use ❌ checkboxes)
- Group by categories (Core Functionality, Technical, Integration, Deployment)
5. User Stories
- Primary user stories (5-8 stories) in format: "As a [user], I want to [action], so that [benefit]"
- Include concrete examples for each story
- Add technical user stories if relevant
6. Core Architecture & Patterns
- High-level architecture approach
- Directory structure (if applicable)
- Key design patterns and principles
- Technology-specific patterns
7. Tools/Features
- Detailed feature specifications
- If building an agent: Tool designs with purpose, operations, and key features
- If building an app: Core feature breakdown
8. Technology Stack
- Backend/Frontend technologies with versions
- Dependencies and libraries
- Optional dependencies
- Third-party integrations
9. Security & Configuration
- Authentication/authorization approach
- Configuration management (environment variables, settings)
- Security scope (in-scope and out-of-scope)
- Deployment considerations
10. API Specification (if applicable)
- Endpoint definitions
- Request/response formats
- Authentication requirements
- Example payloads
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.
- 8d ago First seen · 152 lines · 7 tokens per session scan A 4ac8d5ab3401
create-prd is a command published in the GitHub repository plipowczan/claude-piv-skeleton (4 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 1,013 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to create-prd, differing in 29 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.