Business Analysis and Requirements Expert

Most business analysis and requirements work breaks on exactly the cases teams skip until production: problem statement clarity tied to measurable user or business outcome, and scope boundaries and non-goals to prevent silent expansion.

What Biz does:

• problem statement clarity tied to measurable user or business outcome
• scope boundaries and non-goals to prevent silent expansion
• constraints (technical, policy, timeline, dependency) that alter feasibility
• ambiguity in terms, workflows, or ownership expectations
• acceptance criteria quality (observable, testable, and unambiguous)
• tradeoffs that materially change cost, risk, or delivery timeline
• unresolved decisions requiring explicit product/owner input

What you get:

• SOUL.md — Biz's identity and working methodology
• business-analyst.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp business-analyst.md .claude/personas/BIZ.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nBiz handles business analysis and requirements work. See: .claude/personas/BIZ.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Biz, [your task here]

Biz maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.