--- title: "prd by github · skilld" canonical_url: "https://skilld.dev/gh/github/awesome-copilot/prd" last_updated: "2026-07-27T23:56:07.614Z" meta: description: "Generates structured Product Requirements Documents that map business vision to technical execution, including executive summaries, user stories, acceptance criteria,… From github/awesome-copilot." "og:description": "Generates structured Product Requirements Documents that map business vision to technical execution, including executive summaries, user stories, acceptance criteria,… From github/awesome-copilot." "og:title": "prd by github" "twitter:description": "Generates structured Product Requirements Documents that map business vision to technical execution, including executive summaries, user stories, acceptance criteria,… From github/awesome-copilot." "twitter:title": "prd by github" --- [All skills](https://skilld.dev/skills) [![github avatar](https://github.com/github.png?size=96)github/awesome-copilot repository](https://skilld.dev/gh/github/awesome-copilot) # **/prd** official [github](https://skilld.dev/gh/github)/ [awesome-copilot](https://skilld.dev/gh/github/awesome-copilot) 37,102 4,655 Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis. Updated 18 hours ago Trust [Documentation](https://skilld.dev/skills/tag/documentation "Docs, changelogs, release notes, READMEs") [ prd](https://skilld.dev/skills/tag/prd) [ product-management](https://skilld.dev/skills/tag/product-management) [ requirements](https://skilld.dev/skills/tag/requirements) [ product-planning](https://skilld.dev/skills/tag/product-planning) [ ai-features](https://skilld.dev/skills/tag/ai-features) [ user-stories](https://skilld.dev/skills/tag/user-stories) [ technical-specification](https://skilld.dev/skills/tag/technical-specification) ## Skill content ## Product Requirements Document (PRD) ### Overview Design comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined. ### When to Use Use this skill when: - Starting a new product or feature development cycle - Translating a vague idea into a concrete technical specification - Defining requirements for AI-powered features - Stakeholders need a unified "source of truth" for project scope - User asks to "write a PRD", "document requirements", or "plan a feature" --- ### Operational Workflow #### Phase 1: Discovery (The Interview) Before writing a single line of the PRD, you **MUST** interrogate the user to fill knowledge gaps. Do not assume context. **Ask about:** - **The Core Problem**: Why are we building this now? - **Success Metrics**: How do we know it worked? - **Constraints**: Budget, tech stack, or deadline? #### Phase 2: Analysis & Scoping Synthesize the user's input. Identify dependencies and hidden complexities. - Map out the **User Flow**. - Define **Non-Goals** to protect the timeline. #### Phase 3: Technical Drafting Generate the document using the **Strict PRD Schema** below. --- ### PRD Quality Standards #### Requirements Quality Use concrete, measurable criteria. Avoid "fast", "easy", or "intuitive". ``` # Vague (BAD) - The search should be fast and return relevant results. - The UI must look modern and be easy to use. # Concrete (GOOD) + The search must return results within 200ms for a 10k record dataset. + The search algorithm must achieve >= 85% Precision@10 in benchmark evals. + The UI must follow the 'Vercel/Next.js' design system and achieve 100% Lighthouse Accessibility score. ``` --- ### Strict PRD Schema You **MUST** follow this exact structure for the output: #### 1. Executive Summary - **Problem Statement**: 1-2 sentences on the pain point. - **Proposed Solution**: 1-2 sentences on the fix. - **Success Criteria**: 3-5 measurable KPIs. #### 2. User Experience & Functionality - **User Personas**: Who is this for? - **User Stories**: `As a [user], I want to [action] so that [benefit].` - **Acceptance Criteria**: Bulleted list of "Done" definitions for each story. - **Non-Goals**: What are we NOT building? #### 3. AI System Requirements (If Applicable) - **Tool Requirements**: What tools and APIs are needed? - **Evaluation Strategy**: How to measure output quality and accuracy. #### 4. Technical Specifications - **Architecture Overview**: Data flow and component interaction. - **Integration Points**: APIs, DBs, and Auth. - **Security & Privacy**: Data handling and compliance. #### 5. Risks & Roadmap - **Phased Rollout**: MVP -> v1.1 -> v2.0. - **Technical Risks**: Latency, cost, or dependency failures. --- ### Implementation Guidelines #### DO (Always) - **Define Testing**: For AI systems, specify how to test and validate output quality. - **Iterate**: Present a draft and ask for feedback on specific sections. #### DON'T (Avoid) - **Skip Discovery**: Never write a PRD without asking at least 2 clarifying questions first. - **Hallucinate Constraints**: If the user didn't specify a tech stack, ask or label it as `TBD`. --- ### Example: Intelligent Search System #### 1. Executive Summary **Problem**: Users struggle to find specific documentation snippets in massive repositories. **Solution**: An intelligent search system that provides direct answers with source citations. **Success**: - Reduce search time by 50%. - Citation accuracy >= 95%. #### 2. User Stories - **Story**: As a developer, I want to ask natural language questions so I don't have to guess keywords. - **AC**: - Supports multi-turn clarification. - Returns code blocks with "Copy" button. #### 3. AI System Architecture - **Tools Required**: `codesearch`, `grep`, `webfetch`. #### 4. Evaluation - **Benchmark**: Test with 50 common developer questions. - **Pass Rate**: 90% must match expected citations. Source: [SKILL.md on GitHub](https://github.com/github/awesome-copilot/blob/03986ae177602317067149832a73afec7bacb3dc/skills/prd/SKILL.md) ## What it does Generates structured Product Requirements Documents that map business vision to technical execution, including executive summaries, user stories, acceptance criteria, and risk analysis. Includes a discovery phase to interrogate requirements and a strict schema enforcing measurable success criteria over vague language. Based on the current SKILL.md. ## Frequently asked
Does this skill work for non-software products? The skill is designed for software systems and AI-powered features. It may not fit well for hardware, physical products, or domains outside software development.
Do I need to provide all the context upfront, or will the skill ask clarifying questions? The skill explicitly requires a discovery phase where it interrogates you about the core problem, success metrics, and constraints before drafting. You should expect follow-up questions.
Can this skill generate PRDs for existing products or only new ones? The skill is designed for starting new product or feature development cycles and translating ideas into specifications. It does not describe support for auditing or revising existing PRDs.
What if I haven't decided on a tech stack yet? The skill instructs you to ask or label undefined constraints as `TBD` rather than assume or hallucinate technical details.
Based on the current SKILL.md. These answers refresh after source changes. ## Related skills [![github avatar](https://github.com/github.png?size=48) /multi-stage-dockerfile github/awesome-copilot Create optimized multi-stage Dockerfiles for any language or framework](https://skilld.dev/gh/github/awesome-copilot/multi-stage-dockerfile) [![github avatar](https://github.com/github.png?size=48) /chrome-devtools github/awesome-copilot Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.](https://skilld.dev/gh/github/awesome-copilot/chrome-devtools) [![github avatar](https://github.com/github.png?size=48) /postgresql-optimization github/awesome-copilot PostgreSQL-specific development assistant focusing on unique PostgreSQL features, advanced data types, and PostgreSQL-exclusive capabilities. Covers JSONB operations, array types, custom types, range/geometric types, full-text search, window functions, and PostgreSQL extensions ecosystem.](https://skilld.dev/gh/github/awesome-copilot/postgresql-optimization) [![github avatar](https://github.com/github.png?size=48) /conventional-commit github/awesome-copilot Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.](https://skilld.dev/gh/github/awesome-copilot/conventional-commit) [![github avatar](https://github.com/github.png?size=48) /dotnet-best-practices github/awesome-copilot Ensure .NET/C# code meets best practices for the solution/project.](https://skilld.dev/gh/github/awesome-copilot/dotnet-best-practices) [![github avatar](https://github.com/github.png?size=48) /sql-optimization github/awesome-copilot Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Provides execution plan analysis, pagination optimization, batch operations, and performance monitoring guidance.](https://skilld.dev/gh/github/awesome-copilot/sql-optimization)