Creates a structured PRD from discovery notes with acceptance criteria.
npx skills add https://github.com/tabooes/pm_skills --skill prd-development-tabooes
Please help me install this Agent Skill. Skill: prd-development Source: https://github.com/tabooes/pm_skills/tree/main/skills/prd-development Command: npx skills add https://github.com/tabooes/pm_skills --skill prd-development-tabooes
Turning scattered discovery notes into an engineering-ready PRD that clearly links problem, users, solution, and success criteria for major initiatives.
Generate a complete PRD scaffold from discovery notes, including problem, users, solution, success metrics, and acceptance criteria.
High-intent search queries and answers about installing and using this skill.
To turn discovery notes into an engineering-ready PRD, you can use a structured workflow that orchestrates raw research findings into a document covering problem framing, personas, solution overview, success metrics, and acceptance criteria.
A product requirements document for engineering teams should include an executive summary, problem statement, target users, strategic context, solution overview, success metrics, and user stories with acceptance criteria.
Writing success metrics and acceptance criteria from research findings involves converting user discovery notes into actionable requirements through a phased execution scaffold that links target personas to measurable solution outcomes.
Yes, you can generate a PRD scaffold for cross-functional product, design, and engineering teams that aligns stakeholders through structured sections, optional artifacts, and collaboration prompts from executive summary through open questions.
The best way to structure user stories from product discovery research is to apply a phased documentation workflow that translates problem framing and target user definitions into actionable requirements and testable acceptance criteria.
Yes, the PRD workflow supports phased execution from executive summary to open questions, allowing product managers to progressively build out problem statements, solution overviews, and success metrics while incorporating optional artifacts and review steps.
Prorise-coolArticulates user-centered problem statements using an empathy-driven framework capturing persona, outcomes, barriers, causes, and emotional impact.
davzuckyGenerate a structured Product Requirements Document and save it to /tasks/prd-[feature-name].md.
prayceoApply product management frameworks and storytelling templates for stakeholder alignment.
akvoGenerate developer-ready user stories from PRD and architecture documents.
