skills.rest
JCaraballo113
JCaraballo113COMMUNITY
Explore all skills by this author →
GitHub

prd

Generate a structured PRD from a feature prompt and save it to a markdown file.

Updated Jan 12, 2026
Search Tags:#planning#documentation#requirements#PRD#feature#prd#product-management
One-click install
npx skills add https://github.com/JCaraballo113/ralph-cli --skill prd-jcaraballo113
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/JCaraballo113/ralph-cli/tree/main/skills/prd
Command: npx skills add https://github.com/JCaraballo113/ralph-cli --skill prd-jcaraballo113

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly convert a feature concept into a complete, well-structured PRD by guiding through clarifying questions and producing a ready-to-use document.

Core Features & Use Cases

  • Clarifying questions to resolve ambiguity about problem, scope, success criteria, and boundaries with a structured answer format.
  • PRD generation: Produces sections like Introduction, Goals, User Stories, Acceptance Criteria, Functional Requirements, and Non-Goals.
  • Auto-save: Persists the PRD to .agents/tasks/prd-[feature-name].md for traceability.
  • Reusability: Re-generates PRD when inputs are updated or iterated.
  • Use cases: Product managers can quickly document a feature or project requirements.

Quick Start

Provide a feature prompt and the PRD will be generated and saved to .agents/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 PRD from a feature prompt?▼

To generate a PRD from a feature prompt, provide the concept details and the system will ask clarifying questions to resolve ambiguity before producing a structured document. The final PRD is then automatically saved to .agents/tasks/prd-[feature-name].md for traceability.

What sections are included in a generated product requirements document?▼

A generated product requirements document includes Introduction, Goals, User Stories, Acceptance Criteria, Functional Requirements, and Non-Goals. These sections provide a complete and structured layout for detailing feature planning and project requirements.

How do I handle ambiguous scope when writing feature documentation?▼

To handle ambiguous scope when writing feature documentation, the system asks structured clarifying questions about the problem, boundaries, and success criteria. Providing answers in the structured format resolves uncertainty before the final document is generated.

Can I re-generate a PRD when feature requirements are updated?▼

Yes, you can re-generate a PRD when feature requirements are updated or iterated. The system supports reusability by allowing you to provide updated inputs to produce a new version of the requirements document.

Where are generated PRD files saved for project planning?▼

Generated PRD files for project planning are saved directly to the .agents/tasks/prd-[feature-name].md directory path. This auto-save mechanism ensures your feature documentation is persisted locally for ongoing traceability.

Related Skills

Explore More Product & Management Skills→
danielcastro-devdanielcastro-dev

speclet-draft

Draft collaborative feature plans with clarifying questions to .speclet/draft.md.

Community
Intermediate
AncienttwoAncienttwo
407

repo-harness-sprint

Convert Product Requirements Documents into sprint backlogs and track tasks.

Community
Advanced
Eigo-Mt-FujiEigo-Mt-Fuji

requirements-analyst

Convert stakeholder needs into testable requirements and SRS documentation.

Community
Advanced
ssdiwussdiwu
4

dprd

Analyzes product requirements and planning using competitor, user, and prioritization frameworks.

Community
Advanced