Product Requirements Document (PRD)
Checked<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Install on your platform
Showing OpenClaw.
- 1
Run this in your terminal
terminal$
What we know about this skill
Publisher
product-on-purpose
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned product-on-purpose/pm-skills at 1cef1a9eae.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 1cef1a9eae
- Manifest
- skills/deliver-prd/SKILL.md
- Scanned
- 5 files, 909 lines
About this skill
What it does
This skill generates a Product Requirements Document (PRD) based on provided context and desired outcomes. It structures the document with sections like Goals, Target Audience, Features, Release Criteria, and Open Questions. The generated PRD serves as a clear guide for engineering, design, and other stakeholders involved in product development.
When to use it
- New Product Definition: Use this skill when you're starting from scratch and need to define the scope and requirements of a new product or feature.
- Feature Expansion: Generate a PRD to clearly outline the needs for expanding an existing product with new functionality.
- Alignment Across Teams: Create a shared understanding amongst product, engineering, design, and marketing teams by documenting all requirements in one place.
- Prioritization & Roadmap Planning: The resulting PRD helps prioritize features and inform roadmap development decisions.
Key capabilities
- Generates comprehensive PRDs with standard sections (Goals, Target Audience, Features, Release Criteria, Open Questions).
- Structures information logically for clarity and ease of understanding.
- Provides a foundation for product development alignment.
Example prompts
- "Generate a PRD for a mobile app that helps users track their daily water intake."
- "Create a PRD outlining the requirements for integrating a new payment gateway into our e-commerce platform."
- “Draft a PRD for a feature allowing users to share content directly to social media from within our application.”
Tips & gotchas
The quality of the generated PRD heavily relies on the clarity and detail provided in the initial prompt. Be as specific as possible about the desired functionality, target audience, and goals.