deviljackni/agentic-ba repository overview

Agentic BA is a structured requirements and business-analysis companion. It leads you through a clear sequence of steps—from understanding the problem to a reviewed requirements package—so nothing important is skipped and decisions stay traceable.

⁠You do not need to be a developer to use a session someone runs for you: you answer questions, choose options, and approve moving forward.

⁠how to setup and run:

You have container engine installed, like docker/docker-desktop or podman,etc

⁠if you use openAI:

docker run --rm -it \
  -e AGENTIC_BA_LLM_PROVIDER=openai \
  -e AGENTIC_BA_LLM_MODEL=gpt-4.1-mini \
  -e OPENAI_API_KEY=sk-... \
  -v "$(pwd)/agentic-ba-workspace:/workspace" \
  deviljackni/agentic-ba:latest start "My business idea"

⁠if you use Anthropic:

docker run --rm -it \
  -e AGENTIC_BA_LLM_PROVIDER=anthropic \
  -e AGENTIC_BA_LLM_MODEL=claude-sonnet-4-20250514 \
  -e ANTHROPIC_API_KEY="sk-ant-..." \
  -v "$(pwd)/agentic-ba-workspace:/workspace" \
  deviljackni/agentic-ba:latest start "My business idea"

⁠Who it is for

• Product owners and BAs who want a repeatable session format instead of ad-hoc workshops and scattered notes.
• Leaders and sponsors who need visibility into what was decided, why, and what is still open.
• Teams kicking off a new initiative, a major change, or a vendor build where clarity up front saves rework later.

⁠Problem it solves

Many discovery efforts jump straight to solutions, lose stakeholder context, or end with slides that no one can implement. Agentic BA keeps the work staged, explicit, and resumable:

• You move through defined stages (intake, problem, stakeholders, current and future state, drafting, quality review).
• Approval gates mean you confirm before the session advances—no silent drift.
• You can pause and come back later; state and a transcript are saved locally.
• Outputs are Markdown artifacts you can share, diff in version control, or paste into other tools.

Optional AI assistance (when configured) can suggest wording or working assumptions; you stay in control of what is accepted.

⁠What a session feels like

1. You start with a short description of your initiative or problem in everyday language.
2. The tool asks focused questions and offers choices—including options like “something else” or “not sure yet,” so you are never forced into a wrong box.
3. When something must be resolved before continuing, you see blockers and can answer, record a working assumption, defer, or pause.
4. At stage boundaries you approve continuation so the record reflects conscious agreement.
5. You end with staged write-ups and a requirements package you can hand to engineering, procurement, or leadership.

⁠What you get when you are done

Everything for a session lives under one folder (by default .agentic-ba/sessions/<session-id>/—on the host when you use a container volume mount, or on the machine where the CLI ran):

• Transcript of the conversation-style flow.
• Stage artifacts (intake, problem, stakeholders, current state, future state, requirements draft, review).
• Requirements package (and related exports, depending on workflow)—suitable as the single “source of truth” for that discovery pass.

Your organization can store that folder in shared drive, Git, or a document system—whatever fits your governance.

⁠Today: container-native CLI

The intended way to run Agentic BA is inside a container on a desktop or server. The application and its dependencies execute only in that environment—not as arbitrary installs on someone’s laptop—while a bind-mounted folder on the host receives the session outputs (by default the .agentic-ba/ tree: state, transcript, and Markdown artifacts). That split gives you isolation for execution and simple, portable artifacts you can back up, commit, or drop into shared storage.

You still use a terminal session attached to the container (for prompts and approvals). That fits privacy-sensitive work, repeatable builds, and ops teams who already standardize on images.

If you are not the person starting the container, a typical pattern is: someone on your team runs Agentic BA (often via Docker), mounts a folder your org controls, shares their screen or the exported docs, and checks the artifacts into your normal documentation flow.

⁠Roadmap (where I'm going)

These items are planned directions, not promises on a fixed date:

Feedback on which integrations matter most to your team helps prioritize the roadmap. and if people download this image and tried out find it useful and has more feature request, email: [email protected]⁠