prd

Draft comprehensive PRDs from interviews and codebase analysis.

12|1|Updated Feb 13, 2026

Search Tags:#planning #requirements #interview #prd #product-management #codebase-analysis #module-design

Ready to run

npx skills add https://github.com/helderberto/agent-skills --skill prd-helderberto

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting a new feature or major change requires clear problem framing, stakeholder alignment, and a concrete plan to guide design and implementation.

Core Features & Use Cases

Interactive idea gathering from interviews and codebase exploration.
Guided PRD generation with module design and implementation planning.
Output saved to .specs/prds/<slug>.md and reusable across teams for alignment.

Quick Start

Provide an idea to start and run the plan workflow to generate the PRD.

Frequently Asked Questions about prd

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

FAQPage Schema

How do I draft a PRD from stakeholder interviews and codebase analysis?▼

Drafting a PRD from interviews and codebase analysis involves an interactive process that gathers ideas through guided discovery, explores the existing codebase, and generates a structured document with problem statements and module design saved to .specs/prds/<slug>.md.

What's the best way to structure a product requirements document for a major refactor?▼

The best way to structure a product requirements document for a major refactor is to guide discovery across product, design, and engineering, ensuring the PRD includes structured problem statements, stakeholder-focused outcomes, module interfaces, and implementation planning.

Can I generate module design and implementation plans for cross-team initiatives?▼

Yes, you can generate module design and implementation plans for cross-team initiatives by running a guided workflow that aligns stakeholders and outputs a comprehensive PRD with defined module interfaces and implementation steps.

When do I need a structured PRD for new feature work instead of a simple task description?▼

You need a structured PRD for new feature work when the initiative requires clear problem framing, stakeholder alignment across product and engineering, and a concrete plan with module interfaces to guide design and implementation.

Does this PRD workflow save outputs in a format reusable across engineering teams?▼

Yes, the PRD workflow saves outputs as markdown files in the .specs/prds/<slug>.md directory, making the generated product requirements documents directly reusable across teams for alignment.