bmad-agent-analyst

To turn vague business needs into precise requirements, prompt the analyst with a brief stakeholder need to elicit structured requirements, generating clear briefs, user stories, and decision-ready recommendations.

Requirements traceability tracks stakeholder needs through structured documentation. By capturing stakeholder interviews and elicitation sessions, you produce evidence-based artifacts that ensure repeatable traceability from need to specification.

Yes, you can generate a well-scoped product requirements document from a brainstorming session by providing the brainstorming notes to the analyst for domain knowledge integration and requirements elicitation.

Yes, this approach supports market research synthesis and competitive analysis. It integrates domain knowledge into stakeholder documentation to produce decision-ready recommendations and structured analysis artifacts.

The best way to structure user stories from stakeholder interviews is using persona-driven workflows. This ensures repeatable, evidence-based outputs by transforming elicited stakeholder needs into clear, formal specifications.