How to Use Claude as a Business Analyst: The Elena Skill Guide

Between a stakeholder saying “we need a new system” and a team building the right thing sits a lot of unglamorous, decisive work: pinning down what is really needed, mapping how things work today, and writing it down so nobody builds the wrong thing. When people use Claude as a business analyst with a loose prompt, they get a generic requirements template. A real AI business analyst starts by interrogating the request, not formatting it.

Elena is that analyst. She is a business-analysis persona you load once into Claude, ChatGPT, or any AI chat, and she resists the urge to document the first thing she is told. Her instinct is to separate the stated need from the real one — because the request a stakeholder makes is rarely the problem they actually have.

Why generic AI business analysis falls flat

Unguided, a chatbot accepts the stated need at face value and produces a tidy requirements document for the wrong problem. It reaches for generic templates regardless of context, skips the work of mapping how a process actually runs today, and jumps straight to a solution before the problem is understood. The output looks like analysis and skips the analysing.

What changes with the Elena skill

Elena elicits requirements with the questions a good analyst asks — who, why, what happens now, what breaks. She maps the current process and the future one so the gap is visible, writes clear user stories with acceptance criteria, and stays solution-neutral until the problem is genuinely understood. The result is documentation a team can build from with confidence rather than a template they have to second-guess.

What it actually produces

Requirements documents, user stories with acceptance criteria, current-and-future process maps, gap analysis, the stakeholder questions worth asking before a single line is built, and structured BRD or FRD outlines. Describe a vague request and she turns it into something specific enough to act on.

How to get the most out of it

Give her the real context — the stakeholders, the constraints, what people actually do today — rather than just the headline ask. Let her ask questions before she documents anything. And keep the problem and the solution apart in your own head as she works; her value is in making sure you are solving the right thing.

Who this is for

Business analysts who want a faster first draft, product owners writing requirements, founders specifying a build for a developer, and operations leads redesigning a process. It works with Claude, ChatGPT, or any AI chat that accepts a system prompt. For the work around it, the work & business skills collection covers strategy, operations, and analysis — each a focused assistant rather than a general chatbot.