write-a-prd

Creates a GitHub-issue-ready PRD from interviews, codebase analysis, and module design.

26|3|Updated Feb 17, 2021
One-click install
npx skills add https://github.com/jbalcomb/ReMoM --skill write-a-prd-jbalcomb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/jbalcomb/ReMoM/tree/main/.claude/write-a-prd
Command: npx skills add https://github.com/jbalcomb/ReMoM --skill write-a-prd-jbalcomb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires GitHub API, and includes scripts (resource) components.

What problem does it solve?

This Skill unit solves the complex and iterative process of creating a Product Requirements Document (PRD) by streamlining user interviews, codebase exploration, and module design directly into a GitHub issue.

Core Features & Use Cases

  • Interview-driven PRD: Initiates a conversation with the user to elicit detailed problem statements and solution ideas.
  • Codebase Analysis: Verifies user assertions and gains insight into the current state of the codebase.
  • Collaborative Design: Conducts deep dives into design decisions with the user, resolving dependencies and ensuring a shared understanding.
  • Module Planning: Outlines major modules to be built or modified, seeking user confirmation and identifying testing requirements.
  • PRD Drafting: Constructs the PRD following a template, ensuring comprehensive problem statements, solutions, user stories, implementation decisions, and testing strategies.
  • Issue Submission: Automates the submission of the PRD as a GitHub issue for seamless tracking and collaboration.

Quick Start

Create a Product Requirements Document for a new feature by running the write-a-prd skill with user interviews, codebase analysis, and module design.

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 product requirements document directly in a GitHub issue?

This Skill facilitates PRD creation by conducting user interviews, analyzing your codebase, and outlining modules before automatically submitting the finalized product requirements document as a GitHub issue.

What is the best way to draft a PRD based on user interviews and codebase analysis?

Drafting a PRD from user interviews and codebase analysis requires a workflow that verifies user assertions against actual code, resolves dependencies collaboratively, and structures the final document using a comprehensive product requirements template.

Can I automate feature planning and module design with GitHub?

Yes, you can automate feature planning with GitHub by using this Skill to outline major modules, identify testing requirements, and submit the finalized feature planning details directly as a GitHub issue.

Does this PRD drafting workflow require GitHub API access to function?

Yes, this PRD drafting workflow requires GitHub API access to verify repository details during codebase analysis and to automate the final submission of the product requirements document as a collaborative issue.

How does codebase analysis improve product requirements document drafting?

Codebase analysis improves product requirements document drafting by validating user interview claims against the current code, ensuring accurate module planning, and identifying precise testing requirements for robust feature planning.