write-a-prd

Interview stakeholders and explore codebases to generate structured GitHub issue PRDs.

4|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/EstebanForge/AGENTS --skill write-a-prd-estebanforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/EstebanForge/AGENTS/tree/main/skills/write-a-prd
Command: npx skills add https://github.com/EstebanForge/AGENTS --skill write-a-prd-estebanforge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Crafting a comprehensive PRD manually can be time-consuming and error-prone, often requiring multiple iterations and coordination. This Skill streamlines the process by guiding users through structured steps involving discussion, exploration, and module design, resulting in clear, well-defined documentation.

Core Features & Use Cases

  • User Interview & Exploration: Facilitates gathering detailed problem insights and verifying assumptions through iterative questioning.
  • Module Design & Decomposition: Supports sketching and validating module boundaries, encouraging deep, testable architecture.
  • PRD Template Generation: Automates the creation of a complete, consistent PRD as a GitHub issue, ensuring all key sections are included for development planning.
  • Use Case: A product manager wants to rapidly generate a detailed PRD for a new feature. They provide high-level requirements, and the Skill guides them through thorough analysis, module breakdown, and formatted documentation.

Quick Start

Ask the AI to help you create a detailed PRD for your new feature or product idea, including problem statement, solution outline, and user stories.

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

To create a product requirements document, the Skill guides you through stakeholder interviews, codebase exploration, and module design to generate a structured PRD. It automates formatting as a GitHub issue, ensuring all key development planning sections are included.

What is the best way to gather requirements and design modules for product planning?

Gathering requirements and designing modules is handled through iterative questioning and boundary sketching. The Skill facilitates detailed problem exploration and validates assumptions, encouraging a deep, testable architecture before generating the final documentation.

Can I generate a PRD as a GitHub issue directly from high-level requirements?

Yes, you can generate a PRD as a GitHub issue directly from high-level requirements. The Skill automates PRD template creation, ensuring your problem statement, solution outline, and user stories are consistently formatted for development planning.

Does this PRD generation process support exploring an existing codebase?

Yes, the PRD generation process supports exploring an existing codebase. It guides users through codebase exploration to inform module decomposition and validate technical assumptions, ensuring the generated requirements align with your current architecture.

How do I structure user stories and problem statements for development planning?

Structuring user stories and problem statements is achieved by providing high-level requirements to the Skill. It guides you through thorough analysis and module breakdown, outputting a complete, consistent PRD template with all necessary development planning sections.

Are there limitations to using automated PRD templates for complex module decomposition?

Automated PRD templates rely on iterative questioning to handle complex module decomposition, but require accurate stakeholder input. While it sketches module boundaries and validates assumptions, extremely ambiguous project scopes may need additional manual refinement before final GitHub issue generation.