Generate Product Requirement Document (PRD) Draft

Generates a comprehensive draft for a Product Requirement Document (PRD) based on user inputs and product context. This skill streamlines the initial PRD creation process, saving product managers significant time.

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

מתי להשתמש

Use this skill when you need a rapid, structured starting point for a new Product Requirement Document, especially when you have a clear vision of the product, its users, and its core functionalities.

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

SKILL.md

--- name: Generate Product Requirement Document (PRD) Draft description: Generates a comprehensive draft for a Product Requirement Document (PRD) based on user inputs and product context. This skill streamlines the initial PRD creation process, saving product managers significant time. --- ## Overview This skill assists Product Managers in quickly generating a structured draft for a Product Requirement Document (PRD). By providing key inputs such as product vision, target audience, core features, and business goals, the skill leverages AI to compile a comprehensive document outline and initial content, significantly accelerating the PRD creation process. ## When to use Use this skill when you need a rapid, structured starting point for a new Product Requirement Document, especially when you have a clear vision of the product, its users, and its core functionalities. It's ideal for kicking off a new product or feature development cycle. ## How it works 1. **Provide Product Details:** The user will be prompted to provide essential information about the product, including: - Product Name - Product Vision/Goal - Target Audience/User Personas - Key Features/Functionality (brief descriptions) - Business Goals/Metrics - Release Timeline (optional) 2. **AI Processing:** The AI will process these inputs, mapping them to standard PRD sections. 3. **Draft Generation:** The skill will output a markdown-formatted PRD draft, including standard sections like: - Introduction (Product Vision, Goals, Scope) - User Stories/Use Cases - Functional Requirements - Non-Functional Requirements (e.g., performance, security) - Technical Considerations (integrations, architecture - high level) - Success Metrics - Future Considerations 4. **Review and Refine:** The user can then review, edit, and expand upon the generated draft. ## Example usage **User Input:** "I need a PRD draft for a new mobile app called 'TaskFlow'. It's designed for busy professionals to manage their daily tasks and projects efficiently. Key features include task creation, due date reminders, project categorization, and team collaboration. Our goal is to increase user productivity by 30% and acquire 10,000 active users in the first six months." **Generated PRD Draft (abbreviated):** ```markdown # Product Requirement Document: TaskFlow Mobile App ## 1. Introduction ### 1.1 Product Vision To empower busy professionals with an intuitive and efficient mobile application that streamlines daily task management and project collaboration, ultimately boosting their productivity. ### 1.2 Goals - Increase user productivity by 30% within three months of consistent use. - Acquire 10,000 active users within the first six months post-launch. ### 1.3 Scope This document outlines the requirements for the initial release of the TaskFlow mobile application, focusing on core task management and basic collaboration features. ## 2. User Stories / Use Cases ### 2.1 Task Management - As a busy professional, I want to quickly create new tasks with titles and descriptions, so I can capture ideas before I forget them. - As a busy professional, I want to set due dates and reminders for my tasks, so I don't miss important deadlines. - As a busy professional, I want to categorize my tasks into projects, so I can keep my work organized. ### 2.2 Team Collaboration - As a team member, I want to invite colleagues to a project, so we can work together on shared goals. - As a team member, I want to assign tasks to other team members, so responsibilities are clear. ## 3. Functional Requirements ### 3.1 Task Creation & Editing - TR1: Users shall be able to create new tasks with a title (mandatory) and description (optional). - TR2: Users shall be able to edit task details (title, description, due date, assignee, project). ### 3.2 Due Dates & Reminders - TR3: Users shall be able to set a due date and time for each task. - TR4: The system shall send push notifications as reminders for upcoming tasks. ### 3.3 Project Management - TR5: Users shall be able to create, name, and delete projects. - TR6: Users shall be able to assign tasks to specific projects. ### 3.4 Collaboration - TR7: Users shall be able to invite other registered users to their projects via email. - TR8: Project creators shall be able to assign tasks within a project to specific team members. ## 4. Non-Functional Requirements ### 4.1 Performance - NFR1: The app should load within 3 seconds on a stable internet connection. - NFR2: Task creation and updates should complete within 1 second. ### 4.2 Security - NFR3: User data and project information shall be encrypted both in transit and at rest. - NFR4: User authentication shall be implemented using industry-standard protocols (e.g., OAuth2). ## 5. Success Metrics - Increase in user productivity (measured by task completion rates and user surveys). - Number of active users (monthly and daily). - User retention rate. - Customer satisfaction (NPS). ## 6. Future Considerations - Integration with other calendar applications. - Advanced reporting and analytics for project progress. - Desktop client functionality. ``` ## References - [Product Requirements Document (PRD) Definition - ProductPlan](https://www.productplan.com/glossary/product-requirements-document-prd/) - [How to Write a PRD - Aha!](https://www.aha.io/blog/how-to-write-a-prd) - [The Ultimate Guide to Product Requirements Documents - Roman Pichler](https://www.romanpichler.com/blog/the-ultimate-guide-to-product-requirements-documents/)