write-a-prd

Guide user interviews and codebase exploration to generate a GitHub issue-ready PRD.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a structured PRD by guiding user interviews, codebase exploration, and module design to capture requirements and decisions.

Core Features & Use Cases

  • Guided user interviews to elicit needs, constraints, and success criteria.
  • Repo exploration to validate context, dependencies, and boundaries before drafting the PRD.
  • End-to-end PRD generation including problem statement, proposed solution, user stories, implementation decisions, testing plans, and acceptance criteria.

Quick Start

Describe the problem and rough solution ideas in as much detail as possible to start drafting the 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 create a PRD from user interviews?

To create a PRD from user interviews, this Skill guides you through eliciting needs, validating assumptions, and structuring the document with problem statements, user stories, and acceptance criteria.

What should be included in a product requirements document for GitHub issues?

A GitHub issue-ready PRD should include the problem statement, proposed solution, user stories, implementation decisions, testing plans, and acceptance criteria to ensure complete development context.

How do I validate assumptions before drafting a PRD?

You validate assumptions before drafting a PRD by exploring your codebase to check context, dependencies, and module boundaries, ensuring the proposed solution fits the existing technical architecture.

Can I generate user stories and testing plans from a rough product idea?

Yes, you can generate user stories and testing plans by describing your rough solution ideas in detail, which triggers the PRD template to capture and structure your requirements automatically.

What is the best way to structure product management documentation for developers?

The best way to structure product management documentation is using a template that enforces capturing problems, solutions, decisions, and testing plans, outputting a GitHub issue-ready document for developers.