← Back to library

Business Analyst

Requirements, process maps, and tickets. Done properly.

AvailableProduct & Engineeringv1.0.23

About this persona

Elicits and documents atomic, testable requirements (BRDs, FRSs, traceability matrices), maps as-is and to-be processes in BPMN with assumptions flagged, manages tickets from discovery to definition-of-ready, and builds stakeholder maps and business cases. Never invents requirements, process steps, or ROI numbers.

What it does

  • Draft well-formed tickets from discovery notes and check definition-of-ready
  • Synthesize stakeholder input into BRDs, FRSs, and a traceability matrix
  • Map as-is and to-be BPMN processes with gap analysis
  • Stakeholder and RACI mapping plus cost-benefit business cases
  • Write-backs and sign-off routing behind a human confirmation gate

Commands and examples

Every capability below is a skill in the plugin. Run it directly with its namespaced slash command, or just describe what you want in plain language and the matching skill activates on its own, both work.

Get help and onboarding

Run this any time in Claude Code. It explains the persona and how to run any capability below.

/business-analyst:help-ba

Eliciting and documenting requirements

Synthesizes stakeholder input into structured needs, drafts a BRD/FRS with atomic and testable requirements, and builds a requirements traceability matrix.

Run it directly

/business-analyst:eliciting-and-documenting-requirements

Or just describe what you want

Turn these stakeholder interview notes into a BRD with a traceability matrix: [paste notes].

Mapping and improving processes

Models the current-state process in BPMN-as-text, designs the future-state process, and runs a gap analysis between them.

Run it directly

/business-analyst:mapping-and-improving-processes

Or just describe what you want

Map the current invoice approval process as an as-is BPMN diagram and flag the gaps.

Analyzing stakeholders and the business case

Maps stakeholders on a power/interest grid with a RACI, drafts a cost-benefit business case, and routes deliverables for sign-off.

Run it directly

/business-analyst:analyzing-stakeholders-and-business-case

Or just describe what you want

Build a RACI map and a cost-benefit business case for this project: [describe project].

Managing tickets

Drafts well-formed tickets from discovery output, checks definition-of-ready completeness, summarizes changes for write-back, and analyzes dependencies.

Run it directly

/business-analyst:managing-tickets

Or just describe what you want

Draft a ticket from these discovery notes: [paste notes], and check it against definition of ready.

Install in Claude Code

/plugin marketplace add roleplugin/personas-marketplace
/plugin install business-analyst@personas-marketplace

Requires an active subscription. Prefer not to use GitHub? Download the zip from your library instead.

How to use it

Install the persona, then either ask Claude for the kind of work it covers in plain language, or run a capability directly as its namespaced slash command, /business-analyst:<skill-name>. Every RolePlugin persona also ships a built-in help guide, /business-analyst:help-ba, so you can run it any time to see what the persona can do and how to work with it.