prd-generator
0This skill generates comprehensive Product Requirements Documents (PRDs) that guide development teams and align stakeholders. It is aimed at product managers who need clear, actionable documents based on targeted discovery questions.
191260Updated Today
Product Management
Quick InstallView Source
$ npx skills add https://github.com/jamesrochabrun/skills --skill prd-generatorOverview
About This Skill
The prd-generator skill creates structured Product Requirements Documents that serve as blueprints for development teams and align all stakeholders around project goals. It guides product managers through targeted discovery questions to capture essential requirements, constraints, and success criteria. The skill produces clear, actionable PRDs that reduce ambiguity and accelerate development cycles. Product managers use this skill to document product vision, define scope, outline user stories, and establish measurable success metrics in a standardized format. By automating PRD creation, teams save time on documentation while ensuring comprehensive coverage of all critical product aspects.
How to Use
Install by running `$ npx skills add https://github.com/jamesrochabrun/skills --skill prd-generator`.
Use Cases
Create a PRD for a user authentication feature.
Generate a PRD for a new product launch.
Develop a PRD for feature enhancements based on user feedback.
Create PRDs in various formats, including one-pagers and technical variants.
Tags
Setup & Installation
Quick Install
Terminal
$ npx skills add https://github.com/jamesrochabrun/skills --skill prd-generatorAlternative Install (Git Clone)
git clone https://github.com/jamesrochabrun/skillsRequirements
- Claude Code or compatible AI agent
Quick Start Guide
1
Install the Skill
Copy the install command above and run it in your terminal.
2
Open Your AI Agent
Launch Claude Code, Cursor, or your preferred AI coding agent.
3
Try It Out
Use the prompt template or examples below to test the skill.
4
Customize
Adapt the skill to your specific use case and workflow.
Usage Examples
Prompt Template
Generate a comprehensive Product Requirements Document (PRD) for [PRODUCT_NAME], a [PRODUCT_TYPE] designed for [TARGET_USERS] in the [INDUSTRY] industry. Focus on [KEY_FEATURES] and address the following core questions: 1. What problem does this solve for [TARGET_USERS]? 2. How will success be measured (KPIs)? 3. What are the technical constraints and dependencies? 4. Who are the key stakeholders, and what are their priorities? 5. What are the risks and mitigation strategies? Include sections for user stories, acceptance criteria, and a high-level timeline. Prioritize clarity and actionability for [COMPANY]'s development team.
Example Output
## Product Requirements Document (PRD) **Product Name:** SmartInventory Pro **Product Type:** AI-Powered Inventory Management System **Target Users:** Mid-sized e-commerce retailers with 50+ SKUs **Industry:** Retail & E-commerce --- ### **1. Overview & Problem Statement** SmartInventory Pro solves the critical pain point of **stockouts and overstocking** for e-commerce businesses, which currently cost retailers an average of **$1.1 trillion globally** in lost sales and excess inventory (source: McKinsey, 2023). By leveraging AI-driven demand forecasting and real-time analytics, the system reduces inventory costs by **30%** while improving order fulfillment rates to **98%+**. --- ### **2. Key Features & User Stories** - **AI Demand Forecasting:** Predicts stock needs 30 days in advance with 92% accuracy. - **Automated Reordering:** Triggers purchase orders when inventory dips below safety thresholds. - **Supplier Performance Dashboard:** Tracks lead times, quality scores, and pricing trends. - **Multi-Channel Sync:** Integrates with Shopify, WooCommerce, and Amazon Seller Central. **User Stories:** - *As a warehouse manager, I want automated reorder alerts so I can reduce manual checks by 50%.* - *As a procurement lead, I want supplier performance metrics so I can negotiate better terms.* --- ### **3. Success Metrics (KPIs)** | Metric | Target | Current Baseline | Timeframe | |--------|--------|------------------|-----------| | Order Fulfillment Rate | 98% | 87% | 6 months | | Excess Inventory Days | <15 days | 28 days | 12 months | | Stockout Incidents | <2/month | 8/month | 3 months | --- ### **4. Technical Constraints** - **API Integrations:** Must support RESTful APIs for Shopify, WooCommerce, and Amazon. - **Data Retention:** Historical sales data must be stored for 24 months. - **Scalability:** System must handle 10,000+ SKUs without performance degradation. --- ### **5. Stakeholders & Priorities** | Stakeholder | Priority | Key Concerns | |-------------|----------|--------------| | CFO | High | ROI within 18 months | | Warehouse Team | High | Reduce manual data entry | | Procurement Team | Medium | Supplier performance visibility | --- ### **6. Risks & Mitigation** - **Risk:** Low adoption by warehouse staff due to resistance to change. **Mitigation:** Conduct training sessions and pilot with a small team first. - **Risk:** Inaccurate demand forecasts due to seasonal spikes. **Mitigation:** Incorporate external market trend data (e.g., Google Trends, industry reports). --- ### **7. Timeline** - **Phase 1 (Discovery):** 4 weeks (Stakeholder interviews, data analysis) - **Phase 2 (MVP):** 8 weeks (Core AI forecasting + reordering) - **Phase 3 (Scaling):** 12 weeks (Supplier dashboard, multi-channel sync) --- **Next Steps:** - Finalize technical architecture with the engineering team. - Schedule a workshop to align warehouse and procurement teams on new workflows. *Prepared by: Alex Chen, Product Manager* *Last Updated: October 10, 2023*
Find the right skills for your stack
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan