skills.rest
SyloRei
SyloReiCOMMUNITY
Explore all skills by this author →
GitHub

prd

Generate structured PRDs with goals, user stories, and technical considerations.

3|Updated Mar 22, 2026
Search Tags:#planning#documentation#requirements#pipeline#feature#prd#product-management
One-click install
npx skills add https://github.com/SyloRei/claude-godmode --skill prd-sylorei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/SyloRei/claude-godmode/tree/main/skills/prd
Command: npx skills add https://github.com/SyloRei/claude-godmode --skill prd-sylorei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often spend excessive time drafting Product Requirements Documents (PRDs) from vague ideas. This skill automates the creation of clear, actionable PRDs from concise prompts, aligning stakeholders and speeding up planning.

Core Features & Use Cases

  • Structured PRD templates: Includes sections for Goals, User Stories, Success Criteria, Technical Considerations, and Metrics to standardize planning.
  • Clarifying questions workflow: Proactively asks 3-5 essential questions to disambiguate scope before generating the PRD.
  • Quality gate awareness: Detects project quality commands and records them in the Technical Considerations section for downstream execution.
  • Output management: Saves PRDs to the .claude-pipeline/prds/ directory as prd-[feature-name].md for traceability.

Quick Start

Provide a feature description and let the PRD generator create the document in the .claude-pipeline/prds directory.

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

Yes, you can update an existing PRD mid-roadmap. Provide your new feature details or changes, and the generator will revise the Product Requirements Document, ensuring updated success criteria and technical considerations are captured for the project pipeline.

What sections are included in a generated PRD for feature planning?▼

Before generating a PRD, the tool proactively asks 3-5 clarifying questions to disambiguate scope. It also detects project quality gates and records them in the Technical Considerations section for downstream execution.

Where are generated Product Requirements Documents saved?▼

Generated Product Requirements Documents are saved to the .claude-pipeline/prds directory. The output file is automatically named prd-[feature-name].md to maintain traceability across your project pipeline.

Can I use this to plan new features across different teams?▼

Yes, you can plan new features across teams using this PRD generator. It standardizes documentation with structured templates for goals and metrics, ensuring all stakeholders share a clear, actionable understanding of project requirements.

Related Skills

Explore More Product & Management Skills→
DuongMQuangDuongMQuang
6

0-init

Automate project setup by generating CONTEXT.md and OPEN_QUESTIONS.md.

Community
Intermediate
doravidandoravidan

ralph-run

Orchestrate the RALPH autonomous development loop to implement features from a PRD.

Community
Intermediate
davzuckydavzucky

prd

Generate a structured Product Requirements Document and save it to /tasks/prd-[feature-name].md.

Community
Advanced
LLLLimboLLLLimbo

product-prd

Generate a complete PRD wrapped in [PRD]...[/PRD] from clarifying questions.

Community
Basic