skills.rest
lfuuu
lfuuuCOMMUNITY
Explore all skills by this author →
GitHub

write-a-prd

Create a PRD through user interviews and codebase exploration, then submit it as a GitHub issue.

Updated Jun 2, 2026
Search Tags:#feature planning#interview#user stories#prd#product requirements#module design#github issue
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill write-a-prd-lfuuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/lfuuu/claude-rules/tree/main/global-skills/write-a-prd
Command: npx skills add https://github.com/lfuuu/claude-rules --skill write-a-prd-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a Product Requirements Document from scratch is time-consuming and often misses technical context. This Skill guides an AI through a structured process of interviewing you, verifying claims against your actual codebase, and producing a complete PRD published as a GitHub issue. ## Core Features & Use Cases - Structured Interview Process: Iteratively questions you about the problem, solution ideas, and design decisions until a shared understanding is reached. - Codebase Verification: Explores the repository to validate your assumptions and understand the current state of the code before planning. - Deep Module Design: Identifies modules to create or modify, favoring deep modules with simple, testable interfaces, and confirms testing scope with you. - Use Case: You want to plan a new feature for your app. Describe the problem, let the Skill interview you and inspect the repo, and receive a complete PRD with user stories, implementation decisions, and testing decisions filed as a GitHub issue. ## Quick Start Ask the AI to write a PRD for the new feature you have in mind and answer its interview questions.

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 with AI assistance?▼

Provide a detailed description of the problem you want to solve and any solution ideas. The Skill interviews you about each design aspect, explores your codebase to verify assumptions, and produces a complete PRD as a GitHub issue.

What sections does a product requirements document include?▼

The PRD template covers problem description, solution, an extensive numbered list of user stories, implementation decisions, testing decisions, out-of-scope items, and additional notes. It deliberately excludes file paths and code snippets that quickly become outdated.

Can the PRD be published directly to GitHub?▼

Yes, the final PRD is created as a GitHub issue once the interview and design phases are complete. This keeps requirements visible to the team and linked to the repository where implementation happens.

Does the PRD process involve codebase analysis?▼

Yes, the Skill explores the repository to verify your claims and understand the current codebase state before planning. It also identifies deep modules with simple, testable interfaces that can be created or modified.

When should I not use a full PRD workflow?▼

Skip it for small bug fixes or trivial changes where a full interview and requirements document adds overhead. The Skill allows skipping steps you consider unnecessary, but it is designed for planning substantial new features.

Related Skills

Explore More Product & Management Skills→
adrianliechtiadrianliechti
4

write-spec

Convert vague feature ideas into structured PRDs with goals and scope.

Community
Advanced
pwnk77pwnk77
59

Task Manager

Create and track development tasks linked to Product Requirement Documents.

Community
Intermediate
tom-xstom-xs

receiving-code-review

Evaluate code review feedback against architectural decisions before implementation.

Community
Advanced
jerelvelardejerelvelarde
6

create-rfc

Generate structured RFC documents for cross-team technical proposals.

Community
Intermediate