skills.rest
RemseyMailjard
RemseyMailjardCOMMUNITY
Explore all skills by this author →
Website𝕏@remseymailjardGitHub

write-a-prd

Create a PRD with structured sections and output it as a GitHub issue.

Updated Mar 26, 2026
Search Tags:#documentation#requirements#interviews#prd#product-management#github-issues#modular-design
One-click install
npx skills add https://github.com/RemseyMailjard/superpowers --skill write-a-prd-remseymailjard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/RemseyMailjard/superpowers/tree/main/.github/skills/write-a-prd
Command: npx skills add https://github.com/RemseyMailjard/superpowers --skill write-a-prd-remseymailjard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

Core Features & Use Cases

  • Guided user interviews to extract requirements and validate problem statements.
  • Repository exploration and module-design planning to inform implementation decisions.
  • Output a GitHub issue-ready PRD with structured sections: Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, and Out of Scope.

Quick Start

Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema
How do I turn user interviews into a product requirements document?▼

To turn user interviews into a product requirements document, use a guided interview process to extract requirements, validate problem statements, and map out implementation decisions. The resulting PRD includes structured sections like User Stories and Out of Scope.

What's the best way to create a PRD and publish it as a GitHub issue?▼

The best way to create a PRD and publish it as a GitHub issue is to automate the workflow by generating a structured artifact with Problem Statement, Solution, and Testing Decisions sections, then submitting the finalized document directly to your repository.

What sections should be included in a product requirements document for software projects?▼

A product requirements document for software projects should include Problem Statement, Solution, User Stories, Implementation Decisions, Testing Decisions, and Out of Scope sections to align stakeholders and refine feature scope.

Can I use codebase exploration to inform module design when planning a new feature?▼

Yes, you can use codebase exploration to inform module design when planning a new feature. Exploring the repository helps determine technical implementation decisions and structure the PRD accurately for product teams.

Do I need a detailed problem description to start writing a PRD?▼

Yes, you need a detailed problem description to start writing a PRD. Providing a long, thorough explanation of the problem and any potential solution ideas allows the guided interview process to effectively extract and validate requirements.

Related Skills

Explore More Product & Management Skills→
IcekoleIcekole

write-a-prd

Guide PRD creation through user interviews, codebase analysis, and module design.

Community
Intermediate
SamyakJhaveriSamyakJhaveri

to-prd

Synthesize a PRD from conversation and repository context and publish it to the issue tracker.

Community
Advanced
remiconnessonremiconnesson

write-a-prd

Generate a Product Requirements Document through guided problem and solution exploration.

Community
Advanced
mvillmowmvillmow
18

gh-create-pr-linked

Create a GitHub pull request linked to a specified issue.

Community
Basic