write-a-prd

Interview stakeholders, explore the codebase, and generate a PRD as a GitHub issue.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/466852675/Skills-2026 --skill write-a-prd-466852675
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/466852675/Skills-2026/tree/main/write-a-prd
Command: npx skills add https://github.com/466852675/Skills-2026 --skill write-a-prd-466852675

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Crafting a comprehensive Product Requirements Document (PRD) is often time‑consuming and requires coordinated interviews, codebase analysis, and structured writing. This skill streamlines that process, guiding the user through discovery to a ready‑to‑submit PRD.

Core Features & Use Cases

  • Guides the user to provide a detailed problem description and explores the repository to validate assumptions.
  • Conducts an exhaustive interview to define modules, user stories, implementation, testing, and scope decisions.
  • Generates a PRD using a standardized template and creates a GitHub issue to share it with the team.

Quick Start

Ask the write-a-prd skill to draft a PRD for my new feature and open it as a GitHub issue.

Frequently Asked Questions about write-a-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a PRD from stakeholder interviews and open it as a GitHub issue?

To generate a PRD from interviews, this Skill guides you through stakeholder discovery questions, validates assumptions against your codebase, and outputs a structured PRD document directly as a GitHub issue.

What is the best way to structure a PRD with user stories and module design for a new feature?

The best way to structure a PRD is by using a standardized template that defines problem statements, extensive user stories, module design, and implementation and testing scope decisions without including code snippets.

Can I use this PRD generation process to explore my codebase and validate feature requirements?

Yes, you can use this process to explore your codebase, as it validates feature assumptions and defines modules during the exhaustive interview stage before generating the final PRD.

Does generating a PRD this way include code snippets for the implementation scope?

No, generating a PRD this way does not include code snippets, as it strictly focuses on structured problem statements, user stories, and implementation and testing decisions.

How to conduct an exhaustive interview to define scope and testing decisions for a product requirements document?

You conduct the interview by answering guided discovery questions that define problem descriptions, user stories, implementation scope, and testing decisions, which are then formatted into a standardized PRD template.

Why use a standardized PRD template to create a GitHub issue for product management?

You use a standardized PRD template to create a GitHub issue because it streamlines coordinated interviews and codebase analysis into a ready-to-submit document that effectively shares structured feature requirements with your team.