Claude Code turned into a BABOK-based AI analyst that interviews users and gathers requirements

In this case, Claude Code was turned from a general-purpose AI tool into a practical business analyst. The assistant works according to BABOK v3 logic, suggests the next step, asks clarifying questions and helps carry requirements analysis through to a finished result.

The project is called AIналитик, or AInalyst, and its author built it on top of Claude Code for everyday business-analysis tasks. According to the description, the assistant can build stakeholder maps, prepare interviews, record answers, extract requirements from them, and then trace, prioritize and turn them into clear deliverables. Users do not need to start with a rigid form or a ready-made template: they describe the task in plain words, and the system proposes a structure for the work, asks for missing information and turns the conversation into a sequential analytical process.

The key idea is that AIналитик relies not on abstract advice but on the BABOK Guide v3, one of the main bodies of practice for business analysts. The guide runs to more than 500 pages and describes techniques, stages, roles, risks and approaches to working with requirements. In practice, even experienced specialists do not always keep that whole structure in their heads, and the entry barrier is higher still for beginners. By building the methodology into the assistant's behavior, the author achieved a more disciplined workflow: the system does not let users jump over important steps, reminds them of gaps in the analysis and suggests what to do next if they are unsure of the next action.

The approach is interesting not only as a prompting experiment but also as an example of packaging AI professionally for a specific role. Instead of a general chatbot, you get a tool with a working framework, a set of expected deliverables and a clear logic for moving from problem to requirements. For a team, this can mean less chaos at the start of initiatives, more careful recording of agreements with stakeholders and more predictable preparation of materials for development. The format looks especially useful for specialists who understand the subject domain but are not yet confident with formal analytical methods, and so risk missing critical questions during discovery or interviews.

The emphasis on sequence deserves separate mention. In classic analyst work, value comes not only from the final document but from a chain of decisions: whom to interview, which constraints to check, how to separate wishes from mandatory requirements, how to justify a priority and how to link each requirement to a business goal. These transitions are where people most often make mistakes or shorten the process for the sake of speed.

By design, AIналитик inside Claude Code addresses exactly this problem: it keeps the task context, brings the user back to skipped questions and helps turn raw input into a structure fit to hand on to the product team, developers or the client. That makes the tool useful not only for BAs but also for product managers, project managers and founders in the early stages of developing an idea.

It is also important that this is not about replacing a business analyst with one button. Rather, in this configuration Claude Code becomes a co-pilot: it holds the process, lowers the chance of omissions and helps move faster from a vague request to formalized requirements. If such scenarios keep developing, the market will get a new class of vertical AI assistants: not just clever conversation partners, but tools built into specific professions and methodologies.

For business, it is a signal that the value of AI will increasingly be determined not by a model's general erudition but by how deeply it understands the working context of a specific team in daily practice and how well it can deliver results in real work.