business-analyse

Produce a Business Analysis document for Requirements Engineering handoff.

37|6|Updated Nov 2, 2025

Search Tags:#requirements #personas #exploration #business-analysis #hypotheses #stakeholders

Ready to run

npx skills add https://github.com/pssah4/digital-innovation-agents --skill business-analyse

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: business-analyse
Source: https://github.com/pssah4/digital-innovation-agents/tree/main/skills/business-analyse
Command: npx skills add https://github.com/pssah4/digital-innovation-agents --skill business-analyse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps translate fuzzy business problems and stakeholder needs into a structured Business Analysis document that forms the foundation for Requirements Engineering. It guides problem framing, stakeholder mapping, and scope definition across the Explore, Ideation, and Validation phases.

Core Features & Use Cases

Conducts structured interviews to uncover the problem space, stakeholders, and user needs.
Produces a complete BA document as the input for Requirements Engineering, including executive summary, business context, stakeholder and user analyses, risks, constraints, and requirements overview.
Supports the end-to-end V-Model workflow from EXPLORATION through VALIDATION, ensuring traceability from user problems to architectural decisions via ADRs and epics.

Quick Start

Describe the business problem and identify key stakeholders, then I will generate BA artifacts and prepare for RE handoff.

Frequently Asked Questions about business-analyse

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

FAQPage Schema

How do I turn fuzzy business problems into structured requirements for engineering?▼

To turn fuzzy business problems into structured requirements, you must identify stakeholder needs and frame the problem space. This produces a complete Business Analysis document to serve as the direct input for Requirements Engineering.

What is the best way to map stakeholders and define user personas during business analysis?▼

Mapping stakeholders and defining personas during business analysis requires structured interviews to uncover user needs. This process articulates JTBD frameworks and shapes scope, ensuring alignment across exploration and ideation phases.

How do I prepare a Business Analysis document for Requirements Engineering handoff?▼

Preparing a Business Analysis document for handoff involves generating an executive summary, business context, stakeholder analyses, risks, and constraints. This artifact transitions validated problems directly into Requirements Engineering.

Can I use business analysis artifacts for a Simple Test or MVP context?▼

Business analysis artifacts are fully applicable for Simple Test, PoC, and MVP contexts. They guide problem framing, ideation, and validation to shape goals and success metrics across these varying project scales.

How does business analysis maintain traceability from user problems to architectural decisions?▼

Business analysis maintains traceability from user problems to architectural decisions by following an end-to-end V-Model workflow. This ensures validated user needs map directly to ADRs and epics during the engineering handoff.

What do I need to start generating business analysis documents and scope definitions?▼

To start generating business analysis documents, you need to describe the business problem and identify key stakeholders. The tool then performs requirements elicitation and produces the necessary BA artifacts automatically.