prd

Name: prd
Availability: InStock
Author: Radiants

Generate structured PRDs with clarifying questions and save to Markdown.

1|Updated Dec 17, 2025

Search Tags:#planning #documentation #requirements #prd #product-management #user-stories #stakeholders

Ready to run

npx skills add https://github.com/Radiants-DAO/radtools --skill prd-radiants-dao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/Radiants-DAO/radtools/tree/main/.archive/docs-review/skills/ralph/prd
Command: npx skills add https://github.com/Radiants-DAO/radtools --skill prd-radiants-dao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often struggle to rapidly convert vague feature ideas into detailed, aligned requirements, leading to rework and miscommunication.

Core Features & Use Cases

Clarifying questions: generate 3-5 essential questions to resolve ambiguities before drafting requirements
Structured PRD: output includes Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design & Technical Considerations, Success Metrics, Open Questions
Auto-save: PRD is saved to tasks/prd-[feature-name].md for traceability
Use scenarios: ideal for feature planning, project kickoff, and requirements scoping

Quick Start

Provide a feature description and let PRD Generator ask clarifying questions, then review and save the resulting PRD

Frequently Asked Questions about prd

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

FAQPage Schema

How do I generate a structured product requirements document from a vague feature idea?▼

To generate a structured product requirements document, provide a feature description and the system will ask 3-5 clarifying questions to resolve ambiguities, then output a full PRD covering goals, user stories, and functional requirements to align stakeholders.

What sections are included in an automated PRD for new features?▼

An automated PRD for new features includes Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design and Technical Considerations, Success Metrics, and Open Questions to guide development and ensure alignment.

How to align stakeholders and scope requirements for a project kickoff?▼

To align stakeholders and scope requirements for a project kickoff, use a generated PRD that defines user stories, functional boundaries, and non-goals, ensuring all teams share a clear technical and design understanding before development begins.

Does the PRD generation process save the requirements documentation for traceability?▼

Yes, the PRD generation process saves the requirements documentation automatically to a markdown file named tasks/prd-[feature-name].md, ensuring full traceability for product teams during feature planning and project kickoff.

What is the best way to draft user stories and functional requirements for product planning?▼

The best way to draft user stories and functional requirements for product planning is to input a feature prompt, answer clarifying questions to remove ambiguity, and let the system structure the output into actionable development guidelines.

Can I use this PRD generator without prior technical specifications or detailed design documents?▼

Yes, you can use this PRD generator without prior technical specifications because it takes a basic feature description, asks essential clarifying questions, and independently produces design considerations and technical requirements.