Individual skill
product-requirements-document
Write a clear product requirements document that defines the problem, scope, requirements, success measures, risks, and open questions. Use for: product requirements document, PRD, feature specification, engineering handoff.
.grok/skills/product-requirements-document/SKILL.md
Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 14
- Repository last updated
- Oct 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- grok Repository topic
- prompt-engineering Repository topic
- workflow-automation Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,393 bytes
Read excerpt
# Product Requirements Document
## Purpose
Create a decision-ready product specification that explains why work matters, what must be delivered, what is out of scope, and how success will be evaluated without inventing unavailable facts.
## Workflow
1. State the user or business problem, relevant context, and the intended outcome.
2. Define measurable success criteria and identify the evidence or baseline supporting each one.
3. Describe the proposed user-facing behavior and the functional requirements needed to support it.
4. Separate in-scope work, explicit exclusions, assumptions, dependencies, and unresolved questions.
5. Surface non-functional requirements such as accessibility, reliability, privacy, performance, or security only when relevant.
6. Identify risks, owners where known, and validation or rollout considerations.