business-analyst

Validate client information completeness and feasibility before engineering handoff.

47|11|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/buiphucminhtam/forgewright --skill business-analyst-buiphucminhtam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-analyst
Source: https://github.com/buiphucminhtam/forgewright/tree/main/skills/business-analyst
Command: npx skills add https://github.com/buiphucminhtam/forgewright --skill business-analyst-buiphucminhtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gates client information into a formal BRD by validating completeness, consistency, and feasibility before engineering handoff.

Core Features & Use Cases

  • Structured stakeholder discovery, elicitation, evaluation, and gatekeeping to ensure requirements are complete, feasible, and traceable.
  • 6W1H completeness scoring, feasibility assessment, risk/edge-case analysis, and governance to prevent misinterpretation or scope creep.
  • Automatic handoff packaging for PM/Architect with a strict information gate to prevent pass-through of assumptions.

Quick Start

Start by providing a brief project context so the BA can initiate stakeholder discovery and begin structured elicitation.

Frequently Asked Questions about business-analyst

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

FAQPage Schema
How do I validate client requirements completeness before engineering handoff?

Validate client requirements using 6W1H completeness scoring to ensure all dimensions are covered before engineering handoff. This gatekeeping process checks consistency and feasibility to prevent scope creep and misinterpretation downstream.

What is structured elicitation in business analysis?

Structured elicitation is a systematic stakeholder discovery process that gates client information into a formal BRD. It enforces critical evaluation and traceable requirements across PM and Architect roles to ensure complete, feasible project scope.

How do I assess feasibility and analyze edge cases for a BRD?

Assess BRD feasibility by applying critical evaluation and risk analysis to identify edge cases. This gatekeeping step ensures requirements are consistent and technically viable before automatic handoff packaging to engineering teams.

How do I prevent scope creep during stakeholder discovery?

Prevent scope creep during stakeholder discovery by applying strict information gates that block pass-through of assumptions. Enforcing 6W1H completeness and formal evaluation ensures only traceable, validated requirements move to handoff.

Does business analysis gatekeeping work for PM and Architect handoff?

Business analysis gatekeeping works for PM and Architect handoff by packaging validated requirements through a strict information gate. It ensures traceable requirements across roles by preventing assumptions from passing through to engineering.