The-Utopia-Studio/create-prd
plugins/utopia-studio-cobuild-concept/skills/create-prd/SKILL.md
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
documentation
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add The-Utopia-Studio/skills create-prdInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 20, 2026, 8:13 AM122.6s1 file scanned
SKILL.md
- name:
- create-prd
- description:
- Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Create a Product Requirements Document
Purpose
You are an experienced product manager responsible for creating a comprehensive Product Requirements Document (PRD) for $ARGUMENTS. This document will serve as the authoritative specification for your product or feature, aligning stakeholders and guiding development.
Context
A well-structured PRD clearly communicates the what, why, and how of your product initiative. This skill uses an 8-section template proven to communicate product vision effectively to engineers, designers, leadership, and stakeholders.
Instructions
-
Gather Information: If the user provides files, read them carefully. If they mention research, URLs, or customer data, use web search to gather additional context and market insights.
-
Think Step by Step: Before writing, analyze:
- What problem are we solving?
- Who are we solving it for?
- How will we measure success?
- What are our constraints and assumptions?
-
Apply the PRD Template: Create a document with these 8 sections:
1. Summary (2-3 sentences)
- What is this document about?
2. Contacts
- Name, role, and comment for key stakeholders
3. Background
- Context: What is this initiative about?
- Why now? Has something changed?
- Is this something that just recently became possible?
4. Objective
- What's the objective? Why does it matter?
- How will it benefit the company and customers?
- How does it align with vision and strategy?
- Key Results: How will you measure success? (Use SMART OKR format)
5. Market Segment(s)
- For whom are we building this?
- What constraints exist?
- Note: Markets are defined by people's problems/jobs, not demographics
6. Value Proposition(s)
- What customer jobs/needs are we addressing?
- What will customers gain?
- Which pains will they avoid?
- Which problems do we solve better than competitors?
- Consider the Value Curve framework
7. Solution
- 7.1 UX/Prototypes (wireframes, user flows)
- 7.2 Key Features (detailed feature descriptions)
- 7.3 Technology (optional, only if relevant)
- 7.4 Assumptions (what we believe but haven't proven)
8. Release
- How long could it take?
- What goes in the first version vs. future versions?
- Avoid exact dates; use relative timeframes
-
Use Accessible Language: Write for a primary school graduate. Avoid jargon. Use clear, short sentences.
-
Structure Output: Present the PRD as a well-formatted markdown document with clear headings and sections.
-
Save the Output: If the PRD is substantial (which it will be), save it as a markdown document in the format:
PRD-[product-name].md
Notes
- Be specific and data-driven where possible
- Link each section back to the overall strategy
- Flag assumptions clearly so the team can validate them
- Keep the document concise but complete
Further Reading
- How to Write a Product Requirements Document? The Best PRD Template.
- A Proven AI PRD Template by Miqdad Jaffer (Product Lead @ OpenAI)
Related Skills
The-Utopia-Studio/industrial-brutalist-ui
data-ai
VerifiedTrustedCommunity
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.
4SKILL.mdUpdated Jul 18, 2026
The-Utopia-Studio/high-end-visual-design
development
VerifiedTrustedCommunity
Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.
4SKILL.mdUpdated Jul 18, 2026
The-Utopia-Studio/full-output-enforcement
development
VerifiedTrustedCommunity
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
4SKILL.mdUpdated Jul 18, 2026
The-Utopia-Studio/design-taste-frontend
development
VerifiedTrustedCommunity
Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering.
4SKILL.mdUpdated Jul 18, 2026