prd

Generate a structured PRD with goals, user stories, and acceptance criteria.

96|5|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/ArvorCo/Relentless --skill prd-arvorco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/ArvorCo/Relentless/tree/main/.claude/skills/prd
Command: npx skills add https://github.com/ArvorCo/Relentless --skill prd-arvorco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates structured Product Requirements Documents (PRDs) from a feature description, reducing planning ambiguity and accelerating feature planning.

Core Features & Use Cases

  • PRD generation: Produces a complete PRD with goals, user stories, acceptance criteria, and sections.
  • Clarifying questions: Interactively asks 3-5 essential questions to clarify scope before drafting.
  • PRD persistence: Saves the generated PRD to relentless/features/[feature-name]/prd.md for easy reference.

Quick Start

Use the prd skill to generate a PRD for a new feature. Provide a short description of the feature, and the skill will ask clarifying questions and output a ready-to-use PRD blueprint for your team.

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 idea?

To generate a PRD from a feature idea, provide a short feature description and the tool interactively asks 3-5 clarifying questions to define scope before drafting the complete document with goals, user stories, and acceptance criteria.

What sections are included in a generated product requirements document?

A generated product requirements document includes structured sections for project goals, user stories, and acceptance criteria to streamline product planning and reduce ambiguity for the development team.

How do clarifying questions help define user stories and acceptance criteria?

Clarifying questions help define user stories and acceptance criteria by prompting you for essential scope details before drafting, ensuring the resulting product requirements document accurately captures feature requirements.

Can I save a generated PRD directly to a feature directory?

Yes, the generated PRD is automatically saved as a markdown file to a specific feature directory path, ensuring the finalized product requirements document is persisted for easy team reference.

What is the best way to start product planning for a new feature?

The best way to start product planning for a new feature is to submit a brief feature description, which triggers an interactive scoping session that produces a ready-to-use requirements blueprint.

Do I need any specific dependencies to create user stories and acceptance criteria?

No specific dependencies are required to create user stories and acceptance criteria, as the tool operates independently to transform your feature descriptions into structured product requirements documents.