ba-elicitation-review

Score elicitation outputs against an 8-criteria scorecard and list gaps.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill ba-elicitation-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ba-elicitation-review
Source: https://github.com/clovernguyen1010-ship-it/Clover_Nguyen/tree/main/.agent/skills/ba-elicitation-review
Command: npx skills add https://github.com/clovernguyen1010-ship-it/Clover_Nguyen --skill ba-elicitation-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps business analysts systematically review elicitation outputs to identify gaps, inconsistencies, and readiness issues using a formal 8-criteria scorecard.

Core Features & Use Cases

  • 8-criteria scorecard for evaluating elicitation quality (coverage, depth, clarity, conflict detection, hidden assumptions, stakeholder completeness, actionability, and entity-lifecycle)
  • Entity and lifecycle inventory derivation to inform ERD/use cases and master data considerations
  • generation of focused follow-up questions and a documented gap list (P/S/E/C/D) to drive next steps

Quick Start

Review the latest elicitation notes and generate a scorecard, entity-lifecycle table, and follow-up questions; save outputs under docs-BA.

Frequently Asked Questions about ba-elicitation-review

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

FAQPage Schema
How do I review elicitation notes to identify requirement gaps and inconsistencies?

Review elicitation notes by applying an 8-criteria scorecard to evaluate coverage, depth, and clarity. This process identifies inconsistencies and hidden assumptions, generating a structured scorecard and a documented gap list.

What is an entity-lifecycle inventory in business analysis documentation?

An entity-lifecycle inventory is a derived mapping of business entities and their state transitions. It is extracted from stakeholder interviews and raw requirement notes to inform ERD development and master data considerations.

How do I generate follow-up questions after a stakeholder interview?

Generate follow-up questions by analyzing raw elicitation outputs against formal scoring criteria. This identifies missing stakeholder perspectives and lifecycle gaps, producing focused questions to drive next steps.

Can I use a structured scorecard for compliance gap analysis on requirement notes?

Yes, you can use a structured scorecard for compliance gap analysis. It evaluates elicitation outputs against eight criteria to detect conflicts, hidden assumptions, and actionability issues, outputting clearly tagged gaps.

What is the best way to document requirement gaps using a P/S/E/C/D tagging system?

Document requirement gaps by tagging them with P/S/E/C/D categories during elicitation review. This formal scoring mechanism categorizes identified issues and generates actionable questions to resolve them.