Generate Product Requirement Document (PRD) Draft

Generates a first draft of a Product Requirement Document (PRD) based on user inputs for a new feature or product, outlining key sections and content.

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

מתי להשתמש

When you need to quickly generate a foundational PRD to kickstart the product development process or when iterating on new feature ideas.

תגיות: product-management, prd, documentation, product-development, ai-assisted

SKILL.md

--- name: Generate Product Requirement Document (PRD) Draft description: Generates a first draft of a Product Requirement Document (PRD) based on user inputs for a new feature or product, outlining key sections and content. --- ## Overview This skill aids product managers in rapidly drafting comprehensive Product Requirement Documents (PRDs). By taking a few key inputs, it structures and populates a PRD, significantly reducing the initial effort and time spent on documentation. This allows product teams to move faster from ideation to development with a consistent and well-understood foundation. ## When to use Use this skill when you are starting to define a new product or feature and need to quickly outline its purpose, functionality, and requirements. It's ideal for accelerating the early stages of product development or for generating a baseline PRD that can be refined with further detail and team collaboration. ## How it works 1. User provides key details about the product or feature, including its name, target audience, problem it solves, proposed solution, and high-level success metrics. 2. The skill processes these inputs and constructs a PRD draft with essential sections such as Introduction, Goals, User Stories, Functional Requirements, Non-Functional Requirements, and Success Metrics. 3. The generated PRD is presented to the user, ready for review, refinement, and expansion. ## Example usage **User Input:** "Generate a PRD for a new AI-powered email assistant. It should help busy professionals prioritize emails, summarize long threads, and draft quick replies. Target audience: executives, managers. Problem: email overload. Solution: AI for smart inbox management. Success metrics: 20% reduction in time spent on emails per day, 15% increase in email response rate." **Claude's Output (partial PRD draft):** ```markdown # Product Requirement Document: AI-Powered Email Assistant ## 1. Introduction ### 1.1 Purpose The purpose of this document is to define the requirements for the AI-Powered Email Assistant, a new product designed to help busy professionals manage their email more efficiently. ### 1.2 Scope This document covers the core functionalities of the AI-Powered Email Assistant, including email prioritization, thread summarization, and quick reply drafting. ### 1.3 Target Audience The primary target audience for this product includes executives and managers who frequently experience email overload and need intelligent tools to streamline their communication. ## 2. Goals ### 2.1 Business Goals - Increase user productivity by reducing time spent on email. - Enhance user experience by providing intelligent email management solutions. - Establish [Company Name] as a leader in AI-driven productivity tools. ### 2.2 User Goals - Efficiently prioritize important emails. - Quickly grasp the essence of long email threads. - Generate grammatically correct and contextually relevant quick replies. ## 3. Problem Statement Busy professionals often face an overwhelming volume of emails, leading to decreased productivity, missed important communications, and increased stress. Current email clients lack sophisticated AI capabilities to intelligently manage and process this influx of information. ## 4. Proposed Solution An AI-Powered Email Assistant that leverages machine learning to: - Analyze email content and sender reputation to prioritize incoming messages. - Summarize lengthy email threads into concise, actionable points. - Suggest and draft intelligent quick replies based on email context. ## 5. User Stories * **As an executive**, I want an AI to prioritize my emails so I don't miss critical communications. * **As a manager**, I want to quickly summarize long email threads so I can save time understanding context. * **As a professional**, I want the AI to draft quick replies for me so I can respond efficiently. ## 6. Functional Requirements ### 6.1 Email Prioritization - The system shall classify incoming emails into categories (e.g., Urgent, Important, General, Spam). - The system shall learn user preferences for email prioritization over time. - Users shall be able to manually override AI prioritization. ### 6.2 Thread Summarization - The system shall generate concise summaries of email threads longer than [X] emails or [Y] words. - Summaries shall highlight key decisions, action items, and participants. - Users shall be able to request a summary of any email thread. ### 6.3 Quick Reply Drafting - The system shall suggest up to three quick reply options based on the context of the email. - Users shall be able to edit and customize suggested replies. - The system shall learn from user edits to improve future reply suggestions. ## 7. Non-Functional Requirements ### 7.1 Performance - Email prioritization should occur in real-time (< 1 second). - Email summaries should be generated within 5 seconds for threads up to 100 emails. - Quick reply suggestions should appear within 2 seconds of opening an email. ### 7.2 Security - All email data shall be encrypted in transit and at rest. - User privacy shall be maintained in accordance with [relevant regulations, e.g., GDPR, CCPA]. ### 7.3 Scalability - The system shall be able to handle [X] million users concurrently. ## 8. Success Metrics - **20% reduction** in the average time users spend on emails per day within 3 months of launch. - **15% increase** in email response rate for users within 3 months of launch. - 90% user satisfaction rating for quick reply suggestions. - 85% accuracy in email prioritization. ## 9. Future Considerations - Integration with calendar and task management tools. - Support for multiple languages. - Voice-activated commands. ``` ## References - [Product Requirement Document (PRD) Guide](https://www.productplan.com/glossary/product-requirements-document-prd/) - [Writing a Product Requirements Document (PRD) - Atlassian](https://www.atlassian.com/blog/product-management/product-requirements-document) - [The Art of the PRD: A Guide to Product Requirements Documents](https://amplitude.com/blog/product-requirements-document)