Guide structured user interviews to draft PRDs and acceptance criteria.
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-agent-pm-mazenmrad
Please help me install this Agent Skill. Skill: bmad-agent-pm Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-agent-pm Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-agent-pm-mazenmrad
Product teams often struggle to convert scattered insights into a coherent PRD. John helps drive PRD creation through structured interviews, rapid discovery, and stakeholder alignment.
Begin a PRD session by interviewing stakeholders and drafting the initial requirements outline.
High-intent search queries and answers about installing and using this skill.
To create a PRD through user interviews, you guide structured stakeholder conversations to surface needs, synthesize scattered insights, and draft requirements, epics, and acceptance criteria into a coherent document.
The best way to gather product requirements is conducting structured stakeholder interviews that validate assumptions, drive rapid discovery, and align cross-functional teams on minimal scope before drafting the final alignment artifacts.
Writing user stories and acceptance criteria from interview notes involves synthesizing stakeholder responses into structured requirements, validating assumptions through rapid iteration, and translating validated needs into actionable development artifacts.
Yes, you can use it for stakeholder alignment and assumption validation by driving structured questioning sessions that surface constraints, iterate rapidly on minimum scope, and produce aligned requirements for product teams.
To start drafting product requirements from discovery sessions, you need to load the configuration, embody the interview persona, and begin questioning stakeholders to surface initial needs and constraints for the outline.
Structured discovery prevents scope creep by validating assumptions with minimal scope through rapid iteration and stakeholder alignment, ensuring only confirmed needs become epics and acceptance criteria in the PRD.
cshyangPlan and execute a project discovery phase to define requirements and scope.
salazarsebasDecompose product requirements into epics and stories with acceptance criteria.
Exia-thdPlan and execute agile sprints, tasks, and risks for software teams.
EcoPasteHubGuide collaborative product requirements discovery through structured interviews and codebase exploration.
