Generate structured markdown PRDs with user stories and acceptance criteria.
npx skills add https://github.com/MeechYourGoals/Chravel --skill prd-meechyourgoals
Please help me install this Agent Skill. Skill: prd Source: https://github.com/MeechYourGoals/Chravel/tree/main/.claude/plugins/chravel/skills/prd Command: npx skills add https://github.com/MeechYourGoals/Chravel --skill prd-meechyourgoals
This Skill streamlines the creation of detailed Product Requirements Documents (PRDs) for new features, ensuring all necessary information is captured before development begins.
Use the prd skill to create a PRD for the new user profile editing feature.
High-intent search queries and answers about installing and using this skill.
To generate a Product Requirements Document, use a guided conversational approach to define the problem statement, target users, scope, and technical considerations. This process captures all necessary planning details before development begins.
A structured PRD includes sections for Overview, Problem Statement, Target Users, Goals, Non-Goals, User Stories, Technical Approach, Dependencies, and Success Metrics to ensure comprehensive feature planning and technical specification.
Breaking down a feature into independent user stories involves defining acceptance criteria and scope during the PRD generation process. This supports iterative development by segmenting large features into smaller, manageable technical specifications.
Yes, you can use a conversational approach to define technical specifications and acceptance criteria. The guided information gathering prompts you for essential details like tech stack, scope, and success criteria to build the document.
The best way to outline problem statements and target users is through structured PRD generation. This method prompts you for essential feature details, ensuring all necessary information is captured systematically before coding starts.
Generating product requirements does not require predefined technical dependencies. The guided process prompts you to define the tech stack and document dependencies as part of the technical approach section during the conversation.
burgebjCreate structured product requirement documents from feature concepts and product goals.
GuidoBergmanConvert PRDs and architecture documents into epics and user stories with acceptance criteria.
coco-deBreak epics into user stories and sync sprint artifacts with ZenHub.
heltondoriaGuide users through structured questions to generate a PRD.md file.
