write-a-prd

Create a PRD from interviews, codebase exploration, and module design.

6|3|Updated Sep 13, 2017
One-click install
npx skills add https://github.com/tomholford/dotfiles --skill write-a-prd-tomholford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/tomholford/dotfiles/tree/main/claude/skills/write-a-prd
Command: npx skills add https://github.com/tomholford/dotfiles --skill write-a-prd-tomholford

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams translate user insights into a formal Product Requirements Document (PRD) by guiding structured interviews, repository exploration, and module design reasoning, then submitting as a GitHub or Gitea issue.

Core Features & Use Cases

  • Guided interviews to extract needs and constraints.
  • Codebase exploration to align design with existing architecture.
  • PRD drafting and issue submission to GitHub or Gitea for stakeholder alignment.

Quick Start

Describe a user problem and let the flow guide you through interviews, discovery, and PRD drafting.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema
How do I write a PRD from user interviews and codebase exploration?

To write a PRD from user interviews and codebase exploration, use a guided interview flow to extract needs, explore the repository for architectural alignment, and draft structured requirements for stakeholder review.

What is the best way to align stakeholders on new product requirements?

The best way to align stakeholders on new product requirements is drafting a formal PRD and submitting it directly as a GitHub or Gitea issue, ensuring structured design and module reasoning are visible for review.

How does interview-guided design work for product management?

Interview-guided design for product management works by running structured interviews to extract user constraints, sketching module designs based on codebase exploration, and translating those insights directly into a drafted PRD.

Can I submit a drafted PRD as a GitHub or Gitea issue?

Yes, you can submit a drafted PRD as a GitHub or Gitea issue. The workflow integrates issue submission templates to push formalized requirements directly to your repository for stakeholder alignment.

Do I need existing user insights before starting PRD drafting?

You do not need existing user insights before starting PRD drafting. The process begins with a described user problem and guides you through structured interviews to extract needs and constraints dynamically.

When should I use an interview-guided flow over standard PRD templates?

Use an interview-guided flow over standard PRD templates when planning a new feature or updating requirements, as it ensures codebase exploration and module design reasoning align the PRD with existing architecture.