business-analyst

Name: business-analyst
Availability: InStock
Author: ouakar

Formalize client needs into complete, testable requirements using 6W1H.

Updated Mar 25, 2026

Search Tags:#requirements #handoff #elicitation #business-analysis #stakeholders #process-map

Ready to run

npx skills add https://github.com/ouakar/ubinarys-dental --skill business-analyst-ouakar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: business-analyst
Source: https://github.com/ouakar/ubinarys-dental/tree/main/skills/forgewright/skills/business-analyst
Command: npx skills add https://github.com/ouakar/ubinarys-dental --skill business-analyst-ouakar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The BA skill ensures that client requirements are complete, consistent, and feasible before engineering handoff, preventing misinterpretation and costly rework.

Core Features & Use Cases

Structured elicitation using 6W1H to capture complete requirements.
Phase-based BA workflow: Stakeholder analysis, elicitation, red-team evaluation, information gate, and handoff packaging.
Generates traceable artifacts (stakeholder analysis, requirements register, process maps, feasibility reports) for PM/Architect.

Quick Start

Initiate a structured BA elicitation session to produce a complete, validated handoff package.

Frequently Asked Questions about business-analyst

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

FAQPage Schema

How do I formalize client needs into complete, testable requirements before engineering handoff?▼

You can formalize client needs by applying a structured BA workflow that uses 6W1H completeness checks to identify and validate requirements from the initial request. This prevents misinterpretation and costly rework before PM handoff.

What is the best way to structure stakeholder elicitation rounds for business analysis?▼

The best way to structure stakeholder elicitation is through a phase-based workflow including stakeholder analysis, red-team evaluation, and an information gate. This ensures complete requirements capture and generates traceable artifacts like process maps.

How does a business analyst ensure no gaps exist in a requirements register before PM handoff?▼

A business analyst ensures no gaps by enforcing 6W1H completeness, traceability, data-quality checks, and a formal decision-making gate. This gatekeeping process guarantees requirements are consistent and feasible before handoff packaging.

Can I use process maps and feasibility reports to evaluate project risks during requirements elicitation?▼

Yes, you can use generated process maps and feasibility reports to evaluate project risks. The elicitation workflow includes a dedicated red-team evaluation phase to assess feasibility and ensure complete requirement formalization.

Do I need prior stakeholder analysis to start building a requirements register?▼

Yes, stakeholder analysis is the foundational phase of the workflow. Conducting it first ensures that subsequent elicitation rounds capture accurate needs, leading to a validated and complete requirements register for PM handoff.