bmad-agent-analyst

To convert messy needs into precise requirements, use a structured analyst workflow that translates strategic business questions into evidence-grounded specifications. This process guides brainstorming and domain deep-dives to prevent planning drift and hallucination in downstream execution.

Evidence-based market research for product planning is the process of grounding competitive landscape analysis and domain terminology in verified facts rather than assumptions. You need it when translating strategic business questions into actionable specifications to prevent planning drift and hallucination.

To create a PRFAQ or product brief from unstructured ideas, use a persona-driven discovery workflow that routes your input through specialist sub-tasks. This process elicits strategic requirements and maps your target customers, constraints, and risks into structured documentation.

Yes, you can maintain consistent business analysis context across a session by loading persistent, repo-scoped facts from project context files. Applying resolved configuration ensures your evidence-grounded requirements and competitive landscape analysis remain accurate throughout the workflow.

Generating technical feasibility framing requires resolving agent configuration from a customize.toml file and executing activation steps. This setup ensures the specialist sub-skills can load persistent project facts before dispatching your market research or product brief tasks.

The best way to structure competitive landscape analysis for new product specs is through a routed sub-task workflow that enforces an evidence-grounded analyst persona. This approach systematically maps domain terminology and market research into precise requirements for downstream planning.