PlugWiki

prd skill (github/awesome-copilot): interview you, then write a structured product requirements document

Has your agent interview you about a feature, then write a product requirements document in a fixed structure.

Installs
24.2K
on skills.sh
Stars
40.7K
on GitHub
Updated
Oct 2026
last repo commit

prd is a skill in the community github/awesome-copilot collection. When you ask for a PRD, requirements or a feature plan, it first makes the agent ask you questions, at least two, about the core problem, success metrics and constraints. It then drafts the document using a strict five-part schema.

The parts are an executive summary, user experience and functionality, AI system requirements when they apply, technical specifications, and risks with a phased roadmap. It tells the agent to use measurable criteria, to mark unknown tech as TBD, and to show a draft and ask for feedback.

Good for

  • Product managers and founders turning an idea into a spec
  • Engineers who need written requirements before building a feature
  • Teams planning AI-powered features that need an evaluation plan

Install prd

Claude Code

  1. 1

    Copy this prompt.

    Install the prd skill in Claude Code. Run this command:

npx skills add https://github.com/github/awesome-copilot --skill prd

Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

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

Sections in SKILL.md

  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
  15. Implementation Guidelines
  16. DO (Always)

Key facts

Author
Community contribution to github/awesome-copilot (no individual author in SKILL.md)
Installs on skills.sh
24,237 (data from 2026-11-02)
GitHub stars
40,666 for the whole awesome-copilot repo (2026-11-02)
License
MIT (SKILL.md frontmatter)
Last repo commit
2026-10-30
What is inside
1 file: SKILL.md only, no scripts

What it includes

  • Asks about the problem, success metrics and constraints first

    SKILL.md says the agent must interview you before writing and never write a PRD without at least 2 clarifying questions.

    Try: “Write a PRD for a feature that lets customers export their invoices as CSV.”

    Read · Phase 1: discovery interview

  • Maps the user flow and sets non-goals

    Pulls together what you said, finds dependencies and hidden complexity, and lists what you are not building.

    Read · Phase 2: analysis and scoping

  • Writes the PRD in the strict five-part schema

    Executive summary, user experience and functionality, AI system requirements if applicable, technical specifications, and risks with a phased rollout (MVP to v1.1 to v2.0).

    Write · Phase 3: technical drafting

  • Concrete, measurable requirements, no 'fast' or 'intuitive'

    Shows a bad and a good example, such as search returning results within 200ms for a 10k record dataset.

    Read · Quality rules

  • Define testing, iterate, never invent constraints

    For AI features, specify how output quality is tested. If you gave no tech stack, ask or write TBD.

    Read · DO and DON'T list

  • An intelligent search system PRD

    A short sample covering problem, user stories, AI architecture and an evaluation plan.

    Read · Worked example

From the official docs

Questions

What does the prd skill do?

It makes your agent interview you and then write a product requirements document. The document has a fixed structure with measurable success criteria, user stories, non-goals, technical specs and risks.

How do I install it in Claude Code?

Use the install box at the top of this page. The awesome-copilot README documents a Copilot plugin route for Copilot users, not a Claude route.

Does it write files or only text?

SKILL.md does not say where the PRD is saved. It describes producing the document and asking for feedback, so ask your agent to save it to a file if you want one.

Does it need an API key or internet?

SKILL.md names neither. It is one file with no scripts.

Is it by GitHub?

It lives in GitHub's awesome-copilot repo, whose README says its customizations are sourced from third-party developers and should be inspected before installing.

Is it safe?

It is one file of instructions with no scripts. Anything you tell the agent during the interview becomes part of the document, so leave out secrets and confidential figures you would not put in a shared spec.

Information

updated Nov 2, 2026

Repository
github/awesome-copilot
Folder
skills/prd

github/awesome-copilotskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 2
  1. prd SKILL.md · github.com
  2. awesome-copilot README · github.com

Updated Nov 2, 2026.