write-a-prd

Create a markdown PRD from stakeholder interviews and codebase analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams and makers convert ambiguous ideas, user problems, or stakeholder requests into a clear, actionable Product Requirements Document by guiding interviews, validating repository context, and producing implementation-ready decisions.

Core Features & Use Cases

  • Guided problem elicitation: Ask targeted questions to surface the user's goals, constraints, and proposed solutions.
  • Repository-aware validation: Explore the codebase to verify assumptions, identify impacted modules, and surface integration constraints.
  • Module design & testing guidance: Sketch deep, testable modules, document implementation decisions, and recommend testing scope.
  • Use Case: A product manager needs a PRD for a new feature; run the workflow to interview stakeholders, align design decisions, and generate a markdown PRD for review.

Quick Start

Create a PRD for a requested feature by interviewing me about the problem, analyzing the repository, designing modules, and writing the document using the PRD template.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema
How do I create a product requirements document from user interviews and codebase analysis?

To create a product requirements document from user interviews and codebase analysis, this Skill guides targeted stakeholder questions, explores the repository to validate assumptions, and generates an implementation-ready markdown PRD using a built-in template.

What is the best way to translate user problems into testable modules for a new feature?

Translating user problems into testable modules involves conducting user interviews, validating repository context, sketching deep module designs, and documenting implementation decisions to produce a comprehensive PRD.

Can I generate a markdown PRD that includes integration constraints from my existing codebase?

Yes, you can generate a markdown PRD that includes integration constraints by using the repository-aware validation feature, which explores the codebase to identify impacted modules and surface technical limitations during document creation.

How do I conduct guided problem elicitation to scope product work?

To conduct guided problem elicitation for scoping product work, the Skill asks targeted questions to surface the user's goals, constraints, and proposed solutions, then aligns design decisions before writing the final PRD.

Does this PRD generator require any specific dependencies or components to run?

No specific dependencies or components are required to run this PRD generator, allowing product teams to directly initiate stakeholder interviews and codebase exploration without additional environment setup.