write-a-prd

Interview users and explore the codebase to create a structured PRD.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/yckkkk/reo --skill write-a-prd-yckkkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/write-a-prd
Command: npx skills add https://github.com/yckkkk/reo --skill write-a-prd-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a clear, actionable PRD from conversations and codebase exploration to align teammates on scope and goals.

Core Features & Use Cases

  • Structured PRD workflow: captures problem, solution, user stories, decisions, and testing plans.
  • Collaborative interviewing: guides structured user interviews to extract requirements.
  • End-to-end documentation: produces a GitHub issue-ready PRD with sections for problem, solution, user stories, decisions, and notes.
  • Use Case: When starting a new feature, generate a PRD to align stakeholders before development.

Quick Start

Provide a detailed PRD draft by interviewing the user, surveying the repository, and outlining the problem, solution, and acceptance criteria.

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 a feature planning conversation?

Create a PRD by guiding a structured interview to extract requirements, surveying the codebase, and outlining the problem, solution, user stories, and acceptance criteria into a draft document.

What is the best way to write a product requirements document for stakeholder communication?

The best way to write a product requirements document is to structure it with clear problem statements, solutions, testing plans, and implementation decisions to align teammates on scope and goals before development.

Can I generate a GitHub issue-ready PRD directly from product discovery?

Yes, you can generate a GitHub issue-ready PRD directly from product discovery by capturing the conversation, structuring the feature design, and formatting the end-to-end documentation for issues.

Does this PRD workflow include user stories and testing decisions?

Yes, this PRD workflow includes user stories and testing decisions. It structures the feature design to explicitly document problem statements, solutions, implementation decisions, scope, and notes.

How to document implementation decisions and scope when starting a new feature?

Document implementation decisions and scope by exploring the codebase, conducting a collaborative interview, and producing a structured PRD that captures all testing plans and feature notes.