write-a-prd

Name: write-a-prd
Availability: InStock
Author: Apoco

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

4|Updated Feb 18, 2026

Search Tags:#design #planning #requirements #interview #prd #product-management #github-issue

Ready to run

npx skills add https://github.com/apocohq/skills --skill write-a-prd-apocohq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/apocohq/skills/tree/main/skills/write-a-prd
Command: npx skills add https://github.com/apocohq/skills --skill write-a-prd-apocohq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a clear, actionable PRD by interviewing stakeholders, exploring the codebase, and designing modular solutions, then submit it as a GitHub issue.

Core Features & Use Cases

Interview-driven problem definition: guides users to elicit requirements and constraints from stakeholders.
Repo-aware design: analyzes the repository to verify context and dependencies.
Modular design planning: sketches major modules and interfaces to ensure durable implementation.
PRD template generation: outputs a GitHub issue with sections for Problem Statement, Solution, User Stories, and Implementation Decisions.

Quick Start

Describe the problem you want to solve in detail to begin drafting the PRD.

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 stakeholder interviews into a structured PRD?▼

To turn stakeholder interviews into a structured PRD, provide a detailed problem description and access to the codebase. The tool guides requirement elicitation and outputs a ready-to-submit GitHub issue with clear sections for problem, solution, and implementation decisions.

What is the best way to draft a PRD that aligns with my codebase?▼

Drafting a codebase-aware PRD requires analyzing the repository to verify context and dependencies. This approach sketches major modules and interfaces, ensuring the resulting GitHub issue captures durable implementation decisions and accurate scope.

Can I generate a GitHub issue directly from product requirements?▼

Yes, you can generate a GitHub issue directly from product requirements. The process transforms stakeholder input and repo exploration into a ready-to-submit issue containing the problem statement, solution, user stories, and implementation decisions.

Do I need a template to create a PRD for feature proposals?▼

You need a template, a problem description, and codebase access to create a PRD for feature proposals. These inputs facilitate interview-driven problem definition and modular design planning to produce a structured, actionable GitHub issue.

What sections should a product requirements document include for cross-functional reviews?▼

A PRD for cross-functional reviews should include a Problem Statement, Solution, User Stories, and Implementation Decisions. This structure captures the necessary requirements, scope, and success criteria derived from stakeholder interviews and repo exploration.

Why does my PRD lack clear implementation decisions?▼

A PRD lacks clear implementation decisions when it skips repository analysis and modular design planning. By exploring the codebase to verify dependencies and sketching major interfaces, you can ensure durable implementation decisions are captured in the GitHub issue.