Generate AI Product Requirement Document (PRD)

This skill helps product managers generate comprehensive Product Requirement Documents (PRDs) using AI, streamlining the product development process.

תחום: ניהול מוצר

מתי להשתמש

Use this skill when you need a structured and detailed PRD for a new feature or product, saving time and ensuring key aspects are covered.

תגיות: product-management, requirements, prd, ai-powered, documentation

SKILL.md

--- name: Generate AI Product Requirement Document (PRD) description: This skill helps product managers generate comprehensive Product Requirement Documents (PRDs) using AI, streamlining the product development process. --- ## Overview This skill leverages AI to create a detailed Product Requirement Document (PRD) based on a product brief, user stories, and high-level goals. It ensures consistency, completeness, and clarity in communication across product, engineering, and design teams. ## When to use Invoke this skill when you are starting a new product initiative or feature development and need a well-structured PRD quickly. It's particularly useful for product managers who want to standardize their documentation process and reduce manual effort. ## How it works 1. **Input Gathering**: Provide the AI with your product brief, a list of user stories, and any existing high-level product goals or specifications. 2. **AI Analysis and Structure Generation**: The AI analyzes the provided inputs and generates a PRD outline based on best practices, covering sections like Introduction, Goals, User Stories, Technical Requirements, Design Requirements, Success Metrics, and Open Questions. 3. **Content Population**: The AI populates the sections with relevant details extracted from your inputs, ensuring each requirement is clearly articulated. 4. **Draft Review and Refinement**: Review the AI-generated PRD draft. The AI can then iteratively refine sections based on your feedback and additional inputs. 5. **Finalization**: Export the refined PRD in your desired format (e.g., Markdown, Google Docs compatible). ## Example usage **User Input:** "Generate a PRD for a new AI-powered code review feature. Our main goal is to reduce code defects by 15%. Key user stories include developers wanting to get faster feedback on their pull requests, and engineering managers wanting to track code quality metrics. The system should integrate with GitHub and provide inline suggestions." **AI Output (partial):** ```markdown # Product Requirement Document: AI-Powered Code Review ## 1. Introduction This document outlines the requirements for the new AI-Powered Code Review feature, aimed at improving code quality and accelerating the code review process. This feature will provide automated feedback and suggestions to developers directly within their pull requests. ## 2. Goals * Reduce the number of code defects by 15% within 6 months of launch. * Decrease average pull request review time by 20%. * Improve developer satisfaction with the code review process. ## 3. User Stories * **As a Developer**, I want to receive fast, automated feedback on my code changes so I can address issues before human review. * **As a Developer**, I want inline suggestions for common issues so I can quickly apply fixes. * **As an Engineering Manager**, I want to track code quality metrics per team and project so I can identify areas for improvement. ## 4. Technical Requirements * **Integration**: Seamless integration with GitHub pull requests. * **AI Model**: Develop and deploy an AI model capable of identifying common code defects, style violations, and potential performance issues. * **Inline Suggestions**: Provide actionable, inline code suggestions. * **Scalability**: The system must be able to handle a high volume of pull requests. ## 5. Design Requirements * **User Interface**: Intuitive and non-intrusive UI within the GitHub pull request view for displaying AI feedback. * **Customization**: Options for users to configure the types of feedback they receive. ## 6. Success Metrics * Reduction in reported bugs post-release. * Average time to close pull requests. * Developer satisfaction scores. ## 7. Open Questions * How will the AI model be continuously trained and updated? * What specific programming languages will be supported at launch? * What is the strategy for handling false positives from the AI? ``` ## References * [Product Requirements Document (PRD) Template](https://www.productplan.com/glossary/product-requirements-document-prd/) * [How to write a great PRD](https://www.atlassian.com/agile/product-management/requirements)