skills.rest
christopher-buss
christopher-bussCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

write-a-prd

Create a Product Requirements Document via structured interviews and GitHub issue submission.

6|Updated Nov 30, 2025
Search Tags:#code analysis#GitHub#user interviews#feature requests#PRD creation
One-click install
npx skills add https://github.com/christopher-buss/bedrock --skill write-a-prd-christopher-buss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/christopher-buss/bedrock/tree/main/.agents/skills/write-a-prd
Command: npx skills add https://github.com/christopher-buss/bedrock --skill write-a-prd-christopher-buss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps to create a Product Requirements Document (PRD) by guiding users through a structured interview process, codebase analysis, and module design, making it easier to articulate feature requests clearly and efficiently.

Core Features & Use Cases

  • User Interview: Guides the user through a detailed description of the problem and potential solutions.
  • Codebase Exploration: Analyzes the existing codebase to validate assumptions and understand the context.
  • Module Design: Sketches out necessary modules and confirms with the user.
  • PRD Submission: Automates the PRD creation and submission as a GitHub issue.
  • Use Case: For developers looking to document new feature requests or enhancements to existing functionality.

Quick Start

Use the write-a-prd skill to start a new PRD by running the command: write-a-prd --start

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 for a new feature request?▼

To create a PRD for a new feature request, you can use a structured interview process to articulate the problem, analyze the codebase, design modules, and submit the document directly as a GitHub issue.

How do I write a Product Requirements Document that analyzes existing code?▼

Writing a Product Requirements Document that analyzes existing code involves exploring your codebase to validate assumptions, sketching module designs, and confirming details through a structured user interview process.

Can I use codebase analysis to validate assumptions for a PRD?▼

Yes, codebase analysis validates assumptions for a PRD by exploring existing code to understand the context, sketching necessary modules, and confirming the design with the user before submission.

Does this PRD creation process require interaction with GitHub?▼

Yes, this PRD creation process requires interaction with GitHub to standardize feature requests and automate the final PRD submission directly as a GitHub issue.

What is the best way to document feature requests for development environments?▼

The best way to document feature requests for development environments is standardizing them through a structured interview process that guides module design and codebase exploration.

Why does structured user interview help in PRD creation?▼

Structured user interviews help in PRD creation by guiding users through a detailed description of the problem and potential solutions, making it easier to articulate feature requests clearly and efficiently.

Related Skills

Explore More Software Engineering Skills→
dr-codedr-code

github-automation

Automate GitHub issues, pull requests, branches, CI/CD, and deployments via Rube MCP.

Community
Advanced
dokipendokipen
1

github-issues

Manage GitHub issues and coordination tasks using the gh CLI.

Community
Intermediate
0xHoneyJar0xHoneyJar
1

plan-and-analyze

Generate a traceable PRD from project documentation and interview data.

Official
Advanced
max4cmax4c
8

write-prd

Draft structured PRDs with Goals, Requirements, Non-Goals, Constraints, and Approach.

Community
Advanced