Business Analyst

Guide requirements gathering and process optimization across agile or traditional methodologies.

Updated Apr 16, 2026

Search Tags:#documentation #requirements #data-analysis #business-analysis #stakeholders #use-cases #process-modeling

Ready to run

npx skills add https://github.com/jc180105/.opencode --skill business-analyst-jc180105

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Business Analyst
Source: https://github.com/jc180105/.opencode/tree/main/.opencode/skills/business-analyst
Command: npx skills add https://github.com/jc180105/.opencode --skill business-analyst-jc180105

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expert business analyst specializing in requirements gathering, process optimization, and data-driven decision making. Bridges business needs with technical solutions.

Core Features & Use Cases

Requirements gathering and documentation
Process modeling and optimization
Data interpretation to drive decisions
Stakeholder management and alignment

Quick Start

Provide a concise requirements document outline and a process improvement plan based on stakeholder input.

Frequently Asked Questions about Business Analyst

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

FAQPage Schema

How do I write a business requirements document for stakeholder alignment?▼

To write a business requirements document, gather stakeholder input to drive process optimization and data interpretation, producing artifacts like BRDs, FRDs, process diagrams, and user stories for technical alignment.

What is process modeling and how does it optimize business workflows?▼

Process modeling maps business workflows to identify inefficiencies and guide optimization, utilizing data flow diagrams and use cases to bridge operational needs with technical solutions.

Can I generate agile user stories and functional requirements documents from stakeholder input?▼

Yes, you can generate agile user stories and functional requirements documents by analyzing stakeholder input, applying requirements gathering methodologies, and translating business needs into structured technical artifacts.

What is the best way to bridge business needs with technical data-driven solutions?▼

Bridging business needs with technical solutions requires structured requirements analysis, process modeling, and stakeholder alignment across agile or traditional methodologies to deliver actionable data flow diagrams and use cases.

Does this approach to business analysis work with both agile and traditional methodologies?▼

Yes, this business analysis approach applies to both agile and traditional methodologies, guiding requirements gathering and process optimization to produce use cases, user stories, and process diagrams.

When should I use data flow diagrams instead of process diagrams for requirements analysis?▼

Use data flow diagrams during requirements analysis when mapping how information moves through systems, whereas process diagrams are better for modeling operational workflows and stakeholder activities.