Generate a structured PRD from JTBD outcomes with prioritized requirements.
npx skills add https://github.com/xoai/sage --skill prd-xoai
Please help me install this Agent Skill. Skill: prd Source: https://github.com/xoai/sage/tree/main/skills/prd Command: npx skills add https://github.com/xoai/sage --skill prd-xoai
This Skill transforms complex Job-to-be-Done (JTBD) analyses into structured, actionable Product Requirements Documents (PRDs), ensuring product development is grounded in validated customer needs.
Use the prd skill to generate a product requirements document based on the JTBD analysis found in '.sage/docs/jtbd-analysis.md'.
High-intent search queries and answers about installing and using this skill.
To generate a product requirements document from JTBD analysis, provide the high-opportunity outcomes from your Job-to-be-Done research. The system transforms these validated customer needs into structured, prioritized requirements using the MoSCoW framework.
The MoSCoW framework for prioritizing product requirements categorizes features into Must-have, Should-have, Could-have, and Won't-have. This ensures all generated PRD items are traceable to customer needs and properly structured for team alignment.
Yes, a completed JTBD analysis is required to draft this product requirements document. The process specifically transforms high-opportunity Job-to-be-Done outcomes into structured, testable requirements, ensuring development is grounded in validated customer needs.
To structure testable requirements from customer needs, map validated JTBD outcomes to problem statements, goals, and scope. This ensures every requirement is traceable to a specific customer need and prioritized correctly for product management alignment.
This PRD generation approach produces document deliverables, not code. It outputs a structured Product Requirements Document containing problem statements, goals, and prioritized requirements suitable for team alignment before engineering begins.
The best way to align product management teams before design begins is drafting a PRD from validated JTBD outcomes. This grounds development in customer needs by structuring problem statements, goals, and testable requirements into a single document.
slgoodrichDesign structured interview guides with Mom Test, 5 Whys, and JTBD framing.
product-on-purposeGenerate structured Product Requirements Documents with problem statements, goals, and requirements.
adrianliechtiConvert vague feature ideas into structured PRDs with goals and scope.
dinoudonClarify software requirements using structured practices like user-story mapping and BDD/Gherkin.
