Generate structured Product Requirements Documents from feature descriptions.
npx skills add https://github.com/thesammykins/dotfiles --skill prd-thesammykins
Please help me install this Agent Skill. Skill: prd Source: https://github.com/thesammykins/dotfiles/tree/main/.agents/skills/prd Command: npx skills add https://github.com/thesammykins/dotfiles --skill prd-thesammykins
Automates the creation of Product Requirements Documents (PRDs) to accelerate planning, alignment, and handoff across product, design, and engineering teams.
Tell me a feature description and I will generate a complete PRD saved to tasks/prd-[feature-name].md.
High-intent search queries and answers about installing and using this skill.
A Product Requirements Document (PRD) defines feature scope, goals, and user stories to align product and engineering teams. You need a PRD when planning new features, starting projects, or documenting planned work to guide development.
To generate a PRD, provide a feature description and the tool outputs a structured document with Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Open Questions. It saves the file to tasks/prd-[feature-name].md for review.
Yes, the PRD tool guides stakeholders through essential clarifying questions to capture project scope and success criteria. This ensures the generated product requirements document accurately reflects the necessary functional requirements and boundaries.
Yes, this PRD generator provides a clear template and language specifically suitable for junior developers. It translates feature descriptions into actionable documentation with defined user stories and functional requirements to guide development.
The automated PRD structure includes Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Open Questions. These sections ensure comprehensive product specification and alignment across design and engineering teams.
The PRD automation relies entirely on your initial feature description to generate the output. While it structures user stories and functional requirements, you must still resolve the highlighted Open Questions and define Non-Goals manually to ensure accurate scope.
lekmanConvert rough requirements or Jira tickets into a draft PRD with frontmatter.
grenosGenerate a structured PRD markdown file from a feature brief.
zhizhunbaoGenerate sprint backlogs, user stories, and task breakdowns from PRD requirements.
djd1mGenerate an 11-document SPARC PRD package from a product concept.
