# business_requirements_analyst

The business_requirements_analyst Claude Code subagent turns unclear stakeholder requests into testable business requirements. It connects goals to acceptance criteria and flags gaps or conflicting statements.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 776 repo stars
- Author: AgenticOrgLab
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/business_requirements_analyst.md
- Updated: 2026-11-12
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/business-requirements-analyst

## What it does

The subagent turns stakeholder input into a Markdown requirements specification. It covers the problem, goals, out-of-scope items and stakeholders, then lists functional and non-functional requirements with stable identifiers.

It records business rules, constraints, assumptions and unresolved questions. Each acceptance criterion should be observable and testable, with links from requirements to supporting evidence. The agent avoids prescribing technical design unless asked to do so.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/business_requirements_analyst.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/business_requirements_analyst.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/business_requirements_analyst.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/business_requirements_analyst.md

## When to use it
- Turn a vague request into testable requirements
- Resolve conflicting stakeholder statements
- Record assumptions and unanswered questions
- Link acceptance criteria to supporting evidence

## Example prompts
- Turn these meeting notes into a requirements specification with acceptance criteria.
- Review the stakeholder request and flag conflicts and open questions.
- Put the goals, constraints and requirements from these materials into Markdown.

## Similar
- [business-analyst](https://affpapa.org/en/nevibecode/agents/voltagent-community-business-analyst.md) — subagent · 3855 installs
- [bmad-agent-analyst](https://affpapa.org/en/nevibecode/skills/bmad-agent-analyst.md) — skill · 17700 installs
- [startup-business-analyst](https://affpapa.org/en/nevibecode/plugins/startup-business-analyst.md) — plugin · ★ 42780 repo stars
- [babok_analyst](https://affpapa.org/en/nevibecode/plugins/babok-analyst.md) — plugin · ★ 1596 repo stars
- [product-requirements](https://affpapa.org/en/nevibecode/skills/product-requirements.md) — skill · 1300 installs
- [agents-business-finance](https://affpapa.org/en/nevibecode/plugins/agents-business-finance.md) — plugin · ★ 3785 repo stars

From the same set: [agenticorglab/execorchestra](https://affpapa.org/en/nevibecode/by/agenticorglab/execorchestra.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
