prd

Translate product ideas into structured PRDs with user stories and GitHub issues.

20|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/HerbertJulio/specialist-agent --skill prd-herbertjulio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/HerbertJulio/specialist-agent/tree/main/skills/prd
Command: npx skills add https://github.com/HerbertJulio/specialist-agent --skill prd-herbertjulio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate ambiguous product ideas, stakeholder requests, and feature concepts into a structured PRD that includes user stories, acceptance criteria, and GitHub issues, enabling clear alignment between product, design, and engineering teams.

Core Features & Use Cases

  • Generate a complete PRD from a high-level product idea or requirement.
  • Produce user stories with Gherkin-style acceptance criteria and decomposed tasks mapped to issues.
  • Ensure traceability, scope definition, success criteria, and release milestones for planning and execution.

Quick Start

Provide a product idea and receive a structured PRD with user stories and acceptance criteria.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I turn a product idea into a structured PRD with user stories?▼

To generate a structured PRD, provide your high-level product idea to translate it into a complete document featuring problem statements, scope, success criteria, user stories, and acceptance criteria.

What is the best way to write acceptance criteria for product requirements?▼

Writing acceptance criteria for product requirements is best handled using Gherkin-style formatting mapped to decomposed tasks, ensuring clear alignment between product, design, and engineering teams.

Can I generate GitHub issues directly from a product requirements document?▼

Yes, you can generate GitHub issues directly from a product requirements document by decomposing user stories into actionable tasks with clear priorities and traceability.

How does a PRD workflow handle scope definition and release milestones?▼

A standard PRD workflow handles scope definition and release milestones by structuring stakeholder requests into a complete document, ensuring traceability and versioning for planning and execution.

Do I need existing stakeholder requests to define a problem statement?▼

No, you do not need existing stakeholder requests to define a problem statement; you can start with a high-level feature concept or product idea to establish the problem and success criteria.

Why use Gherkin-style acceptance criteria in product management?▼

Using Gherkin-style acceptance criteria in product management ensures that decomposed tasks and user stories have clear, testable conditions, providing precise traceability and alignment for engineering execution.