Generate structured PRDs with requirements, user stories, and acceptance criteria.
npx skills add https://github.com/tobyilee/toby-plugins --skill prd-tobyilee
Please help me install this Agent Skill. Skill: prd Source: https://github.com/tobyilee/toby-plugins/tree/main/plugins/toby-codereview/skills/prd Command: npx skills add https://github.com/tobyilee/toby-plugins --skill prd-tobyilee
Global teams often struggle with producing structured, actionable PRDs that clearly define scope, success criteria, and implementation details, leading to misalignment and rework.
Describe the feature you want PRDed in one sentence, and I will generate a complete, ready-to-implement PRD.
High-intent search queries and answers about installing and using this skill.
A product requirements document (PRD) defines feature scope, success criteria, and implementation details to align teams. You need a PRD when planning a feature to prevent misalignment and rework across global product teams.
To generate a PRD with user stories and acceptance criteria, describe your feature in a sentence. The tool asks clarifying questions to refine scope, then produces a structured PRD saved as tasks/prd-[feature-name].md.
A structured PRD should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions to fully guide implementation and define scope.
Yes, a PRD explicitly establishes non-goals and open questions to set clear boundaries for your development team. Defining these elements prevents scope creep and highlights unresolved technical or design considerations before implementation.
The best way to align teams on feature scope and success metrics is generating a structured PRD. It provides explicit numbered requirements, traceable user stories, and defined success criteria to ensure all stakeholders share the same understanding.
Generating a PRD requires no external frameworks or dependencies. You simply input a feature description, answer guided clarifying questions to refine the scope, and the tool outputs a complete markdown file with traceable requirements.
danielcastro-devDraft collaborative feature plans with clarifying questions to .speclet/draft.md.
Productfculty-aipmBreak features or PRDs into INVEST user stories with Gherkin acceptance criteria.
JingyiWngDecompose product requirements into epics and stories with acceptance criteria.
imonmiConvert PRD, Architecture, and UX artifacts into epics and stories.
