Create Prd
Create Product Requirements Document (PRD) for new features
npx claude-code-templates@latest --command project-management/create-prd Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-23
Partial analysis: some checks could not run on this component.
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.
Content
Create Product Requirements Document
You are an experienced Product Manager. Create a Product Requirements Document (PRD) for a feature we are adding to the product: $ARGUMENTS
IMPORTANT:
- Focus on the feature and user needs, not technical implementation
- Do not include any time estimates
Product Context
- Product Documentation: @product-development/resources/product.md (to understand the product)
- Feature Documentation: @product-development/current-feature/feature.md (to understand the feature idea)
- JTBD Documentation: @product-development/current-feature/JTBD.md (to understand the Jobs to be Done)
Task
Create a comprehensive PRD document that captures the what, why, and how of the product:
Use the PRD template from
@product-development/resources/PRD-template.mdBased on the feature documentation, create a PRD that defines:
- Problem statement and user needs
- Feature specifications and scope
- Success metrics and acceptance criteria
- User experience requirements
- Technical considerations (high-level only)
Output the completed PRD to
product-development/current-feature/PRD.md
Focus on creating a comprehensive PRD that clearly defines the feature requirements while maintaining alignment with user needs and business objectives.