Generate Product Requirements from User Stories

This skill automatically generates detailed product requirements documents (PRDs) from a set of user stories, ensuring comprehensive coverage and reducing manual effort.

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

מתי להשתמש

Use this skill when you have a collection of user stories and need to quickly translate them into structured, actionable product requirements for development teams.

תגיות: product-management, requirements-gathering, user-stories, prd-generation, ai-powered

SKILL.md

--- name: Generate Product Requirements from User Stories description: This skill automatically generates detailed product requirements documents (PRDs) from a set of user stories, ensuring comprehensive coverage and reducing manual effort. --- ## Overview This skill streamlines the process of creating Product Requirements Documents (PRDs) by leveraging AI to interpret and expand upon user stories. It converts raw user stories into a structured format, identifying key features, functional requirements, non-functional requirements, acceptance criteria, and potential dependencies, saving significant time and reducing the risk of missed details. ## When to use Invoke this skill after initial user story creation or refinement sessions. It is particularly useful when transitioning from a discovery phase into detailed planning and development, enabling product managers to rapidly create comprehensive PRDs for engineering teams. ## How it works 1. **Input User Stories:** Provide a list of user stories, ideally following a standard format (e.g., "As a \[user type\], I want to \[goal\], so that \[benefit\]"). 2. **AI Analysis:** The AI will parse each user story, identifying core actions, user types, and desired outcomes. 3. **Requirement Extraction:** The skill extracts and categorizes information into functional and non-functional requirements. 4. **Acceptance Criteria Generation:** For each requirement, the AI suggests detailed acceptance criteria to guide testing and development. 5. **Dependency Identification (Optional):** If prompted, the AI will also attempt to identify potential dependencies between features or external systems. 6. **PRD Generation:** The skill compiles all extracted and generated information into a structured PRD format, including sections for introduction, features, functional requirements, non-functional requirements, and acceptance criteria. ## Example usage **User Input:** ``` User Stories: - As a registered user, I want to manage my profile information, so that I can keep my personal details up-to-date. - As a customer, I want to add items to my shopping cart, so that I can purchase multiple products at once. - As an administrator, I want to view sales reports, so that I can monitor business performance. ``` **Expected Output (Snippet of a generated PRD):** ```markdown # Product Requirements Document: E-commerce Platform V2 ## 1. Introduction This document outlines the product requirements for the next iteration of the E-commerce Platform, focusing on user profile management, shopping cart functionality, and administrative reporting. ## 2. Features ### 2.1 User Profile Management **Description:** Allows registered users to view and update their personal information. #### 2.1.1 Functional Requirements - FR1: Users must be able to edit their name. - FR2: Users must be able to update their email address. - FR3: Users must be able to change their password. - FR4: Users must be able to view their order history. #### 2.1.2 Non-Functional Requirements - NFR1: Profile updates should be processed within 2 seconds. - NFR2: All sensitive user data must be encrypted at rest and in transit. #### 2.1.3 Acceptance Criteria - AC1: Given a registered user, when they navigate to their profile, then they should see their current name, email, and order history. - AC2: Given a registered user, when they update their email to a valid format, then the email should be successfully saved and a confirmation sent. ### 2.2 Shopping Cart Management **Description:** Enables customers to select and accumulate products for purchase. #### 2.2.1 Functional Requirements - FR1: Users must be able to add a product to the cart. - FR2: Users must be able to remove a product from the cart. - FR3: Users must be able to adjust the quantity of a product in the cart. - FR4: The cart must display the total price of all items. #### 2.2.2 Non-Functional Requirements - NFR1: Adding an item to the cart should not take longer than 1 second. - NFR2: The shopping cart state should be persistent across sessions. #### 2.2.3 Acceptance Criteria - AC1: Given a product page, when a user clicks "Add to Cart", then the product should appear in the cart summary. - AC2: Given items in the cart, when the user changes a quantity, then the total price should update accurately. ### 2.3 Sales Reporting (Admin) **Description:** Provides administrators with key insights into sales performance. #### 2.3.1 Functional Requirements - FR1: Administrators must be able to view daily sales figures. - FR2: Administrators must be able to view monthly sales figures. - FR3: Administrators must be able to filter reports by product category. #### 2.3.2 Non-Functional Requirements - NFR1: Sales reports should generate within 5 seconds for up to 1 year of data. - NFR2: Access to sales reports must be restricted to authenticated administrators. #### 2.3.3 Acceptance Criteria - AC1: Given an authenticated administrator, when they access the sales report page, then they should see a default view of daily sales. - AC2: Given a monthly sales report, when the administrator filters by "Electronics", then only sales data for electronics should be displayed. ``` ## References * [User Story Template Best Practices](https://www.atlassian.com/agile/project-management/user-stories) * [Crafting Effective Product Requirements Documents (PRDs)](https://www.productplan.com/glossary/product-requirements-document/) * [Agile Acceptance Criteria Examples](https://www.smartsheet.com/content/acceptance-criteria-best-practices)