Generate structured Product Requirements Documents with clarifying questions and save to Markdown.
npx skills add https://github.com/filipesf/dotfiles --skill prd-filipesf
Please help me install this Agent Skill. Skill: prd Source: https://github.com/filipesf/dotfiles/tree/main/agents/skills/prd Command: npx skills add https://github.com/filipesf/dotfiles --skill prd-filipesf
Product teams often struggle to quickly produce clear, structured Product Requirements Documents (PRDs) that align stakeholders and guide development.
Use the prd skill to generate a PRD for a new feature by providing a feature description such as "Add multi-tenant analytics dashboard" and allowing the skill to ask clarifying questions.
High-intent search queries and answers about installing and using this skill.
To write a product requirements document, provide a feature description like "Add multi-tenant analytics dashboard" and answer 3-5 clarifying questions to resolve ambiguities before generating the structured PRD.
A structured PRD should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, and Success Metrics to ensure complete alignment across stakeholders during project kickoff.
You can capture user stories and acceptance criteria by entering a feature description during planning or specification, which triggers a disciplined workflow that enforces clear, testable criteria for development handoffs.
Yes, you can generate testable functional requirements directly from a feature description, as the workflow automatically prompts essential clarifying questions to resolve ambiguities and establish success criteria before writing.
Generating PRDs this way saves the final structured document directly to tasks/prd-[feature-name].md, ensuring traceability and versioning for product teams documenting requirements after a discovery session.
The best way to align stakeholders on non-goals and design considerations is enforcing a defined PRD structure that explicitly separates non-goals and design considerations alongside success metrics and functional requirements.
Yeachan-HeoGenerate a PRD with goals, constraints, and implementation phases from a project description.
mixomatConvert rough ideas into validated design specifications with iterative sections.
beekeeper-labGenerate traceability matrices mapping user stories and acceptance criteria to test cases.
LazyNinja435Decompose large user stories into smaller, independently valuable increments.
