bmad-agent-pm

To write a PRD that aligns vision with requirements, use a structured product manager persona to conduct requirements discovery, draft the document, and validate it against stakeholder goals. This ensures high-level product goals translate into actionable development artifacts.

Yes, you can validate an existing PRD for completeness by checking its cohesion and verifying alignment between the PRD, UX designs, architecture, and development-ready epics. This identifies gaps and ensures shippable increments.

The best way to break down product requirements into user stories is through a structured product planning workflow that translates validated PRDs into actionable epics. This prevents wasted effort on low-value features and reduces development rework.

Yes, the PRD creation workflow supports mid-implementation course correction by allowing you to edit outdated PRDs and verify alignment between current development artifacts and evolving product goals. This prevents delayed shipments caused by unclear handoffs.

You need a dedicated product manager persona for requirements discovery when your team faces vague product vision, incomplete PRDs, or frequent misalignment between product and development. It drives stakeholder interviews to translate pain points into validated increments.