business-analyst

Document business requirements and map AS-IS/TO-BE processes.

4|1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/xcrrr/claude-skills --skill business-analyst-xcrrr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-analyst
Source: https://github.com/xcrrr/claude-skills/tree/main/skills/business/business-analyst
Command: npx skills add https://github.com/xcrrr/claude-skills --skill business-analyst-xcrrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridge the gap between business problems and technical solutions by documenting clear requirements.

Core Features & Use Cases

  • Structured requirement elicitation and documentation (BRD, use cases)
  • AS-IS / TO-BE process mapping and gap analysis
  • Stakeholder identification, RACI-style accountability, and change management support
  • Templates and guardrails to keep scope aligned with business objectives
  • Example: Create a BRD and process maps from stakeholder interviews to guide a project kickoff

Quick Start

Identify a business problem, gather key stakeholders, and draft a BRD plus AS-IS/TO-BE process maps to define scope.

Frequently Asked Questions about business-analyst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a BRD from stakeholder interviews?

To create a BRD from stakeholder interviews, use structured requirement elicitation to document clear needs and define scope. The skill bridges business problems and technical solutions by enforcing traceability to objectives and standard templates.

What is AS-IS TO-BE gap analysis in process mapping?

AS-IS TO-BE gap analysis in process mapping identifies the differences between current and future states. This skill bridges the gap by documenting structured requirements and modeling stakeholder impact across both analyses.

How do I document use cases and reduce project scope creep?

Document use cases and reduce project scope creep by applying structured templates and guardrails that enforce traceability to business objectives. This approach minimizes rework by keeping requirement elicitation strictly aligned with goals.

Can I use this for stakeholder identification and RACI accountability modeling?

Yes, you can use this for stakeholder identification and RACI-style accountability modeling. It maps stakeholder impact and supports change management to clarify business needs across the project lifecycle.

Does this skill require technical dependencies to map business processes?

No technical dependencies are required to map business processes and document requirements. The skill operates independently to bridge business problems and technical solutions using standard templates and structured outputs.

What is the best way to structure business analysis for project kickoff?

The best way to structure business analysis for project kickoff is to draft a BRD alongside AS-IS and TO-BE process maps. This identifies the business problem, gathers key stakeholders, and enforces objective traceability.