prd
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
- Installs
- 286
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://modelscope.cn --skill prd- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads prd automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Product Requirements Document (PRD)
Overview
Design comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.
When to Use
Use this skill when:
- Starting a new product or feature development cycle
- Translating a vague idea into a concrete technical specification
- Defining requirements for AI-powered features
- Stakeholders need a unified "source of truth" for project scope
- User asks to "write a PRD", "document requirements", or "plan a feature"
Operational Workflow
Phase 1: Discovery (The Interview)
Before writing a single line of the PRD, you MUST interrogate the user to fill knowledge gaps. Do not assume context.
Ask about:
- The Core Problem: Why are we building this now?
- Success Metrics: How do we know it worked?
- Constraints: Budget, tech stack, or deadline?
Phase 2: Analysis & Scoping
Synthesize the user's input. Identify dependencies and hidden complexities.
- Map out the User Flow.
- Define Non-Goals to protect the timeline.
Phase 3: Technical Drafting
Generate the document using the Strict PRD Schema below.
PRD Quality Standards
Requirements Quality
Use concrete, measurable criteria. Avoid "fast", "easy", or "intuitive".
# Vague (BAD)
- The search should be fast and return relevant results.
- The UI must look modern and be easy to use.
# Concrete (GOOD)
+ The search must return results within 200ms for a 10k record dataset.
+ The search algorithm must achieve >= 85% Precision@10 in benchmark evals.
+ The UI must follow the 'Vercel/Next.js' design system and achieve 100% Lighthouse Accessibility score.
Strict PRD Schema
You MUST follow this exact structure for the output:
1. Executive Summary
- Problem Statement: 1-2 sentences on the pain point.
- Proposed Solution: 1-2 sentences on the fix.
- Success Criteria: 3-5 measurable KPIs.
2. User Experience & Functionality
- User Personas: Who is this for?
- User Stories:
As a [user], I want to [action] so that [benefit]. - Acceptance Criteria: Bulleted list of "Done" definitions for each story.
- Non-Goals: What are we NOT building?
3. AI System Requirements (If Applicable)
- Tool Requirements: What tools and APIs are needed?
- Evaluation Strategy: How to measure output quality and accuracy.
4. Technical Specifications
- Architecture Overview: Data flow and component interaction.
- Integration Points: APIs, DBs, and Auth.
- Security & Privacy: Data handling and compliance.
5. Risks & Roadmap
- Phased Rollout: MVP -> v1.1 -> v2.0.
- Technical Risks: Latency, cost, or dependency failures.
Implementation Guidelines
DO (Always)
- Define Testing: For AI systems, specify how to test and validate output quality.
- Iterate: Present a draft and ask for feedback on specific sections.
DON'T (Avoid)
- Skip Discovery: Never write a PRD without asking at least 2 clarifying questions first.
- Hallucinate Constraints: If the user didn't specify a tech stack, ask or label it as
TBD.
Example: Intelligent Search System
1. Executive Summary
Problem: Users struggle to find specific documentation snippets in massive repositories. Solution: An intelligent search system that provides direct answers with source citations. Success:
- Reduce search time by 50%.
- Citation accuracy >= 95%.
2. User Stories
- Story: As a developer, I want to ask natural language questions so I don't have to guess keywords.
- AC:
- Supports multi-turn clarification.
- Returns code blocks with "Copy" button.
3. AI System Architecture
- Tools Required:
codesearch,grep,webfetch.
4. Evaluation
- Benchmark: Test with 50 common developer questions.
- Pass Rate: 90% must match expected citations.
FAQ
What does the prd skill do?
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
How do I install prd?
Run npx skills add https://modelscope.cn --skill prd in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/prd/ (personal) or .claude/skills/prd/ (project).
Which AI agents can use prd?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is prd safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains prd?
It is published by modelscope.cn in modelscope.cn. It has 286 recorded installs.
More from modelscope.cn
skill-creator
modelscope.cn
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
frontend-design
modelscope.cn
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
pptx-generator
modelscope.cn
Generate, edit, and read PowerPoint presentations. Create from scratch with PptxGenJS (cover, TOC, content, section divider, summary slides), edit existing PPTX via XML workflows, or extract text with markitdown. Triggers: PPT, PPTX, PowerPoint, presentation, slide, deck, slides.
minimax-docx
modelscope.cn
Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three pipelines: (A) create new documents from scratch, (B) fill/edit content in existing documents, (C) apply template formatting with XSD validation gate-check. MUST use this skill whenever the user wants to produce, modify, or format a Word document — including when they say "write a report", "draft a proposal", "make a contract", "fill in this form", "reformat to match this template", or any task whose final output is a .docx file. Even if the user doesn't mention "docx" explicitly, if the task implies a printable/formal document, use this skill.
minimax-pdf
modelscope.cn
Use this skill when visual quality and design identity matter for a PDF. CREATE (generate from scratch): "make a PDF", "generate a report", "write a proposal", "create a resume", "beautiful PDF", "professional document", "cover page", "polished PDF", "client-ready document". FILL (complete form fields): "fill in the form", "fill out this PDF", "complete the form fields", "write values into PDF", "what fields does this PDF have". REFORMAT (apply design to an existing doc): "reformat this document", "apply our style", "convert this Markdown/text to PDF", "make this doc look good", "re-style this PDF". This skill uses a token-based design system: color, typography, and spacing are derived from the document type and flow through every page. The output is print-ready. Prefer this skill when appearance matters, not just when any PDF output is needed.
minimax-xlsx
modelscope.cn
Open, create, read, analyze, edit, or validate Excel/spreadsheet files (.xlsx, .xlsm, .csv, .tsv). Use when the user asks to create, build, modify, analyze, read, validate, or format any Excel spreadsheet, financial model, pivot table, or tabular data file. Covers: creating new xlsx from scratch, reading and analyzing existing files, editing existing xlsx with zero format loss, formula recalculation and validation, and applying professional financial formatting standards. Triggers on 'spreadsheet', 'Excel', '.xlsx', '.csv', 'pivot table', 'financial model', 'formula', or any request to produce tabular data in Excel format.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.