create-prd
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.
Author
Category
Product DesignInstall
Hot:820
Download and extract to your skills directory
Copy command and send to AI Agent for auto-install:
Download and install this skill https://openskills.cc/api/download?slug=phuryn-pm-execution-skills-create-prd&locale=en&source=copy
Create PRD – Product Requirements Document Generator
Skill Overview
create-prd is an AI skill specifically designed to create Product Requirements Documents (PRDs). It uses a proven eight-part template to help you quickly write complete, clear, and easy-to-understand PRDs, effectively aligning the team’s understanding.
Applicable Scenarios
1. Writing Requirements Documents for New Products or Features
When you need to create a formal requirements document for a new product, feature, or product improvement project, this skill can guide you through the complete documentation process—from defining the problem to planning the launch—ensuring that no critical information is overlooked.
2. Preparing Product Feature Specifications
Before development begins, you need to turn a product idea into detailed feature specifications. The template provided by this skill covers core elements such as target users, value proposition, key features, and assumption validation, helping the development team accurately understand the product intent.
3. Reviewing and Improving Existing PRDs
If you already have a product requirements document but want to review and improve it according to a standard framework, this skill can help check whether the document is complete and logically clear, while also providing recommendations for improvement.
Core Features
1. Structured Eight-Part PRD Template
Provides a complete framework comprising an overview, contacts, background, goals, market segmentation, value proposition, solution, and launch plan. Each section includes clear writing guidelines to ensure that the document is both comprehensive and easy to read, making it suitable for engineers, designers, leadership, and various stakeholders.
2. Intelligent Information Collection and Analysis
Supports automatically extracting key information from existing files, research materials, URLs, and customer data. It also guides you to consider core questions: What problem are we solving? Who are we solving it for? How will we measure success? What constraints and assumptions exist? This helps you organize your thoughts before writing.
3. Intelligent Document Generation and Formatting
Based on the information you provide, it automatically generates a properly formatted Markdown document using concise, easy-to-understand language and avoiding industry jargon. The document is automatically saved in the format
PRD-[Product Name].md, making version control and team collaboration easier.Frequently Asked Questions
What Core Sections Should a Product Requirements Document Include?
A complete product requirements document should contain eight key sections: overview (document summary), contacts (stakeholders), background (project context and timing), goals (business objectives and key results), market segmentation (target user groups), value proposition (user benefits and competitive advantages), solution (feature design and technical considerations), and launch plan (release planning). This skill provides detailed writing guidance for each section.
How Do You Define Measurable Success Metrics in a PRD?
In the “Goals” section, use the SMART OKR format to define key results. Ensure that every goal is Specific, Measurable, Achievable, Relevant, and Time-bound. For example: “Increase the user registration conversion rate from 15% to 25% within three months after launch.” Avoid vague statements such as “Improve the user experience.”
Is This Skill Suitable for People Without Product Experience?
Yes. This skill is specifically designed to use language that “a primary school graduate can understand,” avoiding professional jargon and providing detailed writing guidance. It guides you step by step through considering the problem, users, goals, and solution. Even if you have never written a PRD before, you can use this template to generate a complete and logically clear product requirements document. After the document is generated, you can further adjust and improve it according to your actual circumstances.