business-analyst

Translate ambiguous business needs into actionable software requirements and documentation.

Updated Aug 27, 2026

Search Tags:#documentation #requirements #business-analysis #use-cases #stakeholder-management #process-modeling

Ready to run

npx skills add https://github.com/HoaiAn0906/Anki --skill business-analyst-hoaian0906

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: business-analyst
Source: https://github.com/HoaiAn0906/Anki/tree/main/.cursor/skills/business-analyst
Command: npx skills add https://github.com/HoaiAn0906/Anki --skill business-analyst-hoaian0906

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ambiguity in requirements and miscommunication between business stakeholders and developers often lead to scope creep and delays. This Skill helps standardize analysis, capture clear requirements, and align stakeholders to deliver actionable specifications.

Core Features & Use Cases

Requirements elicitation, documentation (BRD/FRS), and use-case development
Process modeling, gap analysis, and traceability
Stakeholder facilitation, sign-off, and governance across product, engineering, and QA Use case example: A team needs to turn a high-level business objective into a BRD and a set of use cases with acceptance criteria, ready for development.

Quick Start

Begin by outlining the project goal and identifying key stakeholders, then run a rapid requirements gathering session using the workshop framework.

Frequently Asked Questions about business-analyst

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

FAQPage Schema

How do I translate ambiguous business needs into clear requirements for software development?▼

To translate ambiguous business needs into clear requirements, identify high-level objectives and key stakeholders, then run a requirements gathering session to produce actionable BRD/FRS specifications and use cases ready for development.

How do I create a BRD and FRS with use cases and acceptance criteria?▼

Creating a BRD and FRS with use cases involves eliciting stakeholder needs, documenting functional requirements, and defining acceptance criteria through process modeling to align product, engineering, and QA teams for delivery.

What is the best way to prevent scope creep caused by miscommunication between business stakeholders and developers?▼

Preventing scope creep caused by stakeholder miscommunication requires standardizing business analysis, capturing clear requirements, and establishing governance with stakeholder sign-off to align teams on actionable specifications.

Can I use BPMN process modeling for gap analysis and requirements traceability?▼

Yes, you can use BPMN process modeling for gap analysis and traceability by mapping current and future states, identifying missing functional requirements, and linking use cases back to original business objectives.

How do I facilitate stakeholder sign-off and governance across product, engineering, and QA teams?▼

Facilitating stakeholder sign-off and governance across product, engineering, and QA teams requires structured workshop frameworks to align on BRD/FRS documentation, verify use cases, and formalize requirements approval.

When do I need formal use-case analysis and stakeholder alignment for my project?▼

You need formal use-case analysis and stakeholder alignment when translating high-level business objectives into development-ready specifications, ensuring engineering and QA teams have clear, actionable requirements with defined acceptance criteria.