write-a-prd

Generate a GitHub issue-ready PRD template through structured discovery and stakeholder interviews.

Updated Oct 22, 2024
One-click install
npx skills add https://github.com/DigiBanks99/dotfiles --skill write-a-prd-digibanks99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/DigiBanks99/dotfiles/tree/main/modules/agents/.config/.agents/skills/write-a-prd
Command: npx skills add https://github.com/DigiBanks99/dotfiles --skill write-a-prd-digibanks99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to articulate and align on a clear PRD. This skill guides structured discovery, stakeholder interviews, and module design, then compiles everything into a GitHub issue-ready document.

Core Features & Use Cases

  • Guided PRD workflow: collects problem statements, proposed solutions, user stories, implementation decisions, testing decisions, scope, and notes in a coherent PRD.
  • Interview-driven requirements: prompts to elicit needs from stakeholders and capture constraints.
  • Modular scoping: identifies major components and dependencies to plan architecture and delivery.
  • GitHub-ready output: formats the PRD as a template suitable for immediate GitHub issue submission.

Quick Start

Provide a detailed problem statement and desired outcomes to begin drafting your PRD.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema
How do I draft a PRD that is ready for a GitHub issue?

To draft a PRD ready for a GitHub issue, this skill automates guided generation through structured discovery, capturing problem statements, user stories, and scope into a formatted template for immediate submission.

What is the best way to conduct stakeholder interviews for product management requirements?

Conducting stakeholder interviews for product management is streamlined through guided prompts that elicit needs and capture constraints, automatically integrating the interview-driven requirements directly into your PRD.

How do I structure a PRD for cross-functional alignment and roadmap creation?

Structure a PRD for cross-functional alignment by identifying major components and dependencies, applying modular scoping to plan architecture and delivery, and compiling everything into a coherent document.

Can I use this to generate user stories and implementation decisions for feature proposals?

Yes, you can generate user stories and implementation decisions for feature proposals by providing a detailed problem statement and desired outcomes to begin the guided PRD drafting workflow.

What do I need to start writing a product requirement document with this approach?

To start writing a product requirement document, you need to provide a detailed problem statement and your desired outcomes, which initiates the structured discovery process to articulate and align on clear requirements.