Agent skill · Code Review & Quality

prd

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

GitHub68,948★ · +463/wk · 2 repos on radarProfile →
copilotMIT
Install
npx skills add github/awesome-copilot --skill prd --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/prd/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 37,432 · +281 this week
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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: Technic

What's inside
Steps it walks through
  1. Overview
  2. When to Use
  3. Operational Workflow
  4. Phase 1: Discovery (The Interview)
  5. Phase 2: Analysis & Scoping
  6. Phase 3: Technical Drafting
  7. PRD Quality Standards
  8. Requirements Quality
  9. Strict PRD Schema
  10. 1. Executive Summary
  11. 2. User Experience & Functionality
  12. 3. AI System Requirements (If Applicable)
  13. 4. Technical Specifications
  14. 5. Risks & Roadmap
More from awesome-copilot
All skills →
About this skill
What does the prd skill do?

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

How do I install it?

Run `npx skills add github/awesome-copilot --skill prd --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going