skills.rest
tomkis
tomkisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

write-a-prd

Draft PRDs from user interviews and codebase exploration.

Updated Aug 23, 2026
Search Tags:#design#requirements#interview#prd#product-management#github-issues#module-design
One-click install
npx skills add https://github.com/tomkis/liftcoach --skill write-a-prd-tomkis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/tomkis/liftcoach/tree/main/.agents/skills/write-a-prd
Command: npx skills add https://github.com/tomkis/liftcoach --skill write-a-prd-tomkis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex features often hinges on capturing user needs, validating context, and aligning stakeholders. This skill guides you through structured user interviews, repository exploration, and modular design to produce a ready-to-submit PRD as a GitHub issue.

Core Features & Use Cases

  • Guided user interviews to elicit problem statements, goals, and constraints.
  • Repository exploration to verify assumptions and capture contextual details from the codebase.
  • Module-design sketching and PRD drafting using the provided template, then submitting as a GitHub issue.

Quick Start

Describe your problem in detail and I will draft a PRD and prepare a GitHub issue draft.

Frequently Asked Questions about write-a-prd

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

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

To draft a PRD from user interviews, you capture problem statements and constraints, explore the repository context to validate assumptions, outline modules, and produce a PRD using a structured template.

What is the best way to structure product requirements for GitHub issue submission?▼

Structuring product requirements for GitHub issues involves outlining modules from your design sketches and fitting captured user problems into a provided PRD template to ensure stakeholder alignment.

Can I use user interviews to validate assumptions before writing a PRD?▼

Yes, user interviews elicit problem statements, goals, and constraints, which you then validate by exploring the repository context to verify assumptions before producing the final PRD.

How do I align stakeholders when planning complex feature modules?▼

Aligning stakeholders for complex feature planning requires drafting a structured PRD that synthesizes validated user problems and codebase context into a ready-to-submit GitHub issue.

Does drafting a PRD require exploring the repository context beforehand?▼

Yes, exploring the repository context beforehand is required to verify assumptions and capture technical details from the codebase, ensuring the PRD accurately reflects module design constraints.

Related Skills

Explore More Product & Management Skills→
mattstrublemattstruble
2

prd-writing

Co-author a Behavioral PRD via structured interviews and codebase exploration, output to docs/prd.md.

Community
Intermediate
apocohqapocohq
4

write-a-prd

Generate a structured PRD as a GitHub issue from stakeholder interviews and repo exploration.

Official
Advanced
tomholfordtomholford
6

write-a-prd

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

Community
Advanced
GenEducationGenEducation

bmad-agent-pm

Clarify product requirements from vague ideas into concise PRDs.

Official
Intermediate