write-a-prd

Convert free-form product plans into structured PRDs with user stories and module design.

139|15|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/maiobarbero/my-ai-workflow --skill write-a-prd-maiobarbero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-prd
Source: https://github.com/maiobarbero/my-ai-workflow/tree/main/skills/write-a-prd
Command: npx skills add https://github.com/maiobarbero/my-ai-workflow --skill write-a-prd-maiobarbero

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a messy free-form plan or feature idea into a clear, unambiguous product requirements document by combining repository exploration with a structured, relentless user interview so implementation decisions are discovered before coding begins.

Core Features & Use Cases

  • Repository-aware discovery: Inspects the codebase to validate assumptions, find affected modules, and surface integration concerns before committing to designs.
  • Relentless interviewing: Walks down each branch of the design tree with the user to resolve dependencies, edge cases, and failure modes until decisions are unambiguous.
  • Module design & testing guidance: Proposes deep modules, interfaces, testing targets, and explicit out-of-scope items so implementation work can be split into verifiable issues and tasks.
  • Use case: Preparing a PRD for a new payment integration where the skill identifies relevant services, asks about actors and failure modes, and produces a complete PRD saved to the repo.

Quick Start

Create a PRD for adding OAuth login, interview me about actors and edge cases, explore the repository for related modules, and save the document to docs/prd/oauth-login.md.

Frequently Asked Questions about write-a-prd

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

FAQPage Schema
How do I write a product requirements document for a new feature?

To write a product requirements document, you start with a free-form plan and use a structured interview process to capture problem statements, user stories, and implementation decisions. The resulting PRD defines module design and testing targets for the new feature.

What should be included in a PRD before coding begins?

A complete PRD should include a problem statement, proposed solution, exhaustive user stories, implementation decisions, module design, testing decisions, and explicit out-of-scope items. Capturing these elements before coding ensures unambiguous implementation requirements.

How do I identify affected modules when planning a feature modification?

You identify affected modules by exploring the codebase during the early design phase. Repository exploration validates assumptions and surfaces integration concerns, ensuring the module design accounts for existing services before implementation starts.

How do you resolve edge cases and failure modes when defining product requirements?

You resolve edge cases and failure modes through relentless interviewing, walking down each branch of the design tree with stakeholders. This resolves dependencies and clarifies implementation decisions until the product requirements are unambiguous.

Can I save a generated PRD directly to my repository?

Yes, you can save the generated PRD directly to your repository. The process writes the finalized product requirements document to a user-specified file path within your project directory, such as docs/prd/feature-name.md.