business

Translate ambiguous business requests into structured, validation-ready requirements and artifacts.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/chrisstineline/CGI_Agent --skill business-chrisstineline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business
Source: https://github.com/chrisstineline/CGI_Agent/tree/main/Business
Command: npx skills add https://github.com/chrisstineline/CGI_Agent --skill business-chrisstineline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns unclear business requests into delivery-ready requirements that stakeholders can validate and teams can implement with confidence.

Core Features & Use Cases

  • Requirement discovery & clarification: Convert vague statements into explicit rules, decisions, assumptions, and open questions while exposing ambiguity instead of hiding it.
  • Structured business artifacts: Produce requirement lists, user stories with measurable acceptance criteria, process flows, decision tables, business rules catalogs, and gap/impact analyses.
  • Stakeholder & validation readiness: Map owners and decision points, separate current vs target state, and ensure each requirement is verifiable.

Quick Start

Ask for a complete requirement set by saying: "Transform this business need into a validated CGI-ready specification with in-scope/out-of-scope, stakeholder mapping, structured requirements, and user stories with acceptance criteria."

Frequently Asked Questions about business

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

FAQPage Schema
How do I turn ambiguous business requests into structured user stories with acceptance criteria?

Gap analysis identifies the differences between current and target state processes. You map existing business rules against target requirements to expose missing functionalities, dependencies, and open questions for stakeholder validation.

What is the best way to document complex business rules using a decision table?

A decision table documents complex business rules by mapping explicit triggers, inputs, logic, and outputs. This structured format separates facts from assumptions, ensuring every condition and resulting action is verifiable for delivery teams.

How do you facilitate requirement gathering workshops to extract clear business specifications?

Requirement gathering workshops extract clear business specifications by guiding stakeholders through ambiguous requests to separate facts from assumptions, mapping decision points, and producing prioritized requirements with defined owners and dependencies.

Can I map stakeholders and define process flows for delivery-ready business analysis?

Yes, you can map stakeholders and define process flows by identifying explicit owners, decision points, and dependencies. This separates current versus target state processes to ensure each business requirement remains verifiable and implementation-ready.

Why does my business analysis produce unvalidatable requirements with hidden assumptions?

Business analysis produces unvalidatable requirements when vague statements hide ambiguity instead of exposing it. You must extract explicit triggers, inputs, logic, and outputs while separating facts from assumptions to ensure validation-ready specifications.