prd-generation

Generate structured PRDs with goals, user stories, and success metrics.

4|2|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/anis-marrouchi/ralf --skill prd-generation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-generation
Source: https://github.com/anis-marrouchi/ralf/tree/main/skills/prd-generation
Command: npx skills add https://github.com/anis-marrouchi/ralf --skill prd-generation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD creation is time-consuming and error-prone. This skill guides you to produce structured, testable requirements that align stakeholders and engineers.

Core Features & Use Cases

  • Structured PRD templates that cover Introduction, Goals, User Stories with acceptance criteria, Functional and Non-Functional Requirements, Non-Goals, and Success Metrics.
  • Clear prioritization guidance and sizing guidance to keep work within a single iteration.
  • Use Case scenarios to convert vague ideas into actionable requirements.

Quick Start

Provide a concise feature description and acceptance criteria to generate the PRD using this guide.

Frequently Asked Questions about prd-generation

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

FAQPage Schema
How do I write a PRD with user stories and acceptance criteria?▼

To write a PRD with user stories and acceptance criteria, provide a concise feature description to generate a structured document covering goals, functional requirements, and testable user stories.

What is the best way to structure product requirements documentation for engineering teams?▼

The best way to structure product requirements documentation is using an end-to-end template that includes introduction, goals, non-goals, technical considerations, and success metrics to align stakeholders and engineers.

How do I convert vague feature ideas into actionable product requirements?▼

You convert vague feature ideas into actionable product requirements by applying prioritization and sizing guidance that breaks down initial concepts into clear, testable requirements within a single iteration.

Does this PRD generation method support feature refactoring planning?▼

Yes, this PRD generation method supports feature refactoring planning by enabling consistent requirements documentation for both new initiatives and existing feature refactors across product teams.

What sections should I include in a product requirements document?▼

A product requirements document should include an introduction, goals, user stories with acceptance criteria, functional and non-functional requirements, non-goals, technical considerations, and success metrics.

Can I generate non-functional requirements and success metrics for my feature plan?▼

Yes, you can generate non-functional requirements and success metrics for your feature plan, as the structured PRD workflow explicitly covers both functional and non-functional aspects alongside measurable success metrics.