Generate structured PRDs with clarifying questions and save to Markdown.
npx skills add https://github.com/Radiants-DAO/radtools --skill prd-radiants-dao
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
Product teams often struggle to rapidly convert vague feature ideas into detailed, aligned requirements, leading to rework and miscommunication.
Provide a feature description and let PRD Generator ask clarifying questions, then review and save the resulting PRD
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
LLLLimboGenerate a complete PRD wrapped in [PRD]...[/PRD] from clarifying questions.
AncienttwoConvert Product Requirements Documents into sprint backlogs and track tasks.
JingyiWngDecompose product requirements into epics and stories with acceptance criteria.
tgmarinhoConvert conversation content into a Product Requirements Document and publish it to an issue tracker.
