Verified:GitHub

prd

Generate a structured PRD from a feature description.

Updated Jan 14, 2026

Search Tags:#documentation #requirements #prd #product-management #user-stories #acceptance-criteria #clarifying-questions

Ready to run

npx skills add https://github.com/battyejp/amp-ralph-api --skill prd-battyejp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/battyejp/amp-ralph-api/tree/main/skills/prd
Command: npx skills add https://github.com/battyejp/amp-ralph-api --skill prd-battyejp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of comprehensive Product Requirements Documents (PRDs) from a feature brief, ensuring teams have a clear, actionable plan before beginning implementation.

Core Features & Use Cases

Clarifying questions: Prompt-driven Q&A to resolve ambiguities.
Structured PRD generation: Provides sections for Introduction, Goals, User Stories, Functional Requirements, Non-Goals, etc.
Deliverables: Saves PRD to tasks/prd-[feature-name].md for easy tracking and handoff.
Use Case: Given a feature idea, generate a PRD you can hand to engineering and product teams.

Quick Start

Use the prd skill to generate a PRD for a feature description. The skill will ask clarifying questions and save to tasks/prd-[feature-name].md.

Frequently Asked Questions about prd

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

FAQPage Schema

How do I generate a product requirements document from a feature brief?▼

To generate a product requirements document, provide a feature description to prompt clarifying questions, which then automatically produce a structured PRD with goals, user stories, and functional requirements. This ensures teams have an actionable plan before implementation begins.

What sections should be included in a PRD for new feature scoping?▼

A PRD for new feature scoping should include an Introduction, Goals, User Stories with acceptance criteria, Functional Requirements, Non-Goals, Design, Technical considerations, success metrics, and open questions to align product and engineering teams effectively.

How do clarifying questions help refine user stories and acceptance criteria?▼

Clarifying questions help refine user stories and acceptance criteria by resolving ambiguities in the initial feature brief through prompt-driven Q&A. This ensures the generated PRD accurately specifies capabilities and aligns team expectations before development.

How are generated PRDs saved for engineering team handoff and tracking?▼

Generated PRDs are saved as markdown files to tasks/prd-[feature-name].md for engineering team handoff and tracking. This deliverable format ensures easy integration into project planning and feature scoping workflows across product lifecycles.

When do I need to define non-goals and technical considerations in product management?▼

You need to define non-goals and technical considerations in product management when scoping new features to prevent scope creep and address implementation constraints. This structured PRD approach ensures clear boundaries and capability specification across teams.