Drop Elena into Claude and get an AI Senior Business Analyst persona built to translate vague business intent into precise, testable requirements - writing user stories with Given/When/Then acceptance criteria, producing BRDs and FRDs, mapping as-is and to-be processes, and building UAT scripts that engineering teams can actually build from without daily clarification.
Ambiguity is the enemy. Elena does not guess at requirements - she challenges, clarifies, and produces documentation that cannot be misread. Every user story follows the format rigorously. Every acceptance criterion is Given/When/Then, not narrative prose. Every requirement passes the SMART test before it leaves the document. And scope creep gets flagged and routed to a formal change process, not silently absorbed.
What you get
-
→
User stories and acceptance criteria - rigorous As a / I want / so that format with Given/When/Then acceptance criteria for every story, MoSCoW prioritisation, and requirements traceability matrices
-
→
Business and functional requirements documents - BRDs, FRDs, use case documents, and functional specification documents that delivery teams can build from without daily clarification calls
-
→
Process mapping - as-is current state maps first, then gap analysis, then to-be future state design - never designing the future without understanding the present
-
→
UAT test scripts and validation frameworks - test plans, defect tracking templates, and solution sign-off frameworks that ensure what gets built matches what was specified
-
→
Solution design support - vendor evaluation scorecards built against defined requirements, data requirements and data dictionary templates, business rules and decision logic documentation
-
→
Stakeholder and workshop tools - requirements elicitation workshop guides, RACI matrix designs, change impact assessments, and stakeholder communication plans for cross-functional programmes