business-analyst

Decompose PRDs into INVEST-aligned user stories and business rules.

Updated Apr 4, 2026

Search Tags:#requirements #glossary #regulatory #user-stories #business-analysis #domain-terms

Ready to run

npx skills add https://github.com/asalhamed/dev-agents --skill business-analyst-asalhamed

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: business-analyst
Source: https://github.com/asalhamed/dev-agents/tree/main/business-analyst
Command: npx skills add https://github.com/asalhamed/dev-agents --skill business-analyst-asalhamed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose PRDs into user stories, model business processes, identify domain terms, map regulatory constraints, and bridge business and technical language.

Core Features & Use Cases

Decompose PRDs into user stories that follow INVEST, with clear acceptance criteria.
Extract and centralize domain terms into a glossary for ubiquitous language.
Map regulatory/compliance requirements to governance artifacts and traceability.
Bridge business and technical language to align product and engineering teams.

Quick Start

Feed the PRD to the analyst skill to generate a structured backlog of user stories and domain terms.

Frequently Asked Questions about business-analyst

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

FAQPage Schema

How do I break down a PRD into actionable user stories?▼

To break down a PRD into actionable user stories, feed the document into the analyst tool to generate an INVEST-aligned backlog. This decomposes product requirements into structured items with clear acceptance criteria and business rules.

What is the best way to extract domain terms for a ubiquitous language glossary?▼

Extracting domain terms for a ubiquitous language glossary involves identifying and centralizing business vocabulary from requirements documents. This bridges business and technical language to align product and engineering teams on definitions.

How do I map regulatory constraints to user stories for traceability?▼

Map regulatory constraints to user stories for traceability by linking compliance requirements directly to governance artifacts. This ensures every regulatory constraint is documented and connected to structured backlog items.

Can I use INVEST principles to structure my product requirements?▼

Yes, you can apply INVEST principles to structure product requirements by decomposing PRDs into structured user stories. This generates actionable backlog items that follow INVEST criteria with clear acceptance criteria.

Does this approach work for bridging business and technical language across teams?▼

Bridging business and technical language works by extracting domain terms into a centralized glossary and modeling business processes. This aligns product owners and engineering teams by translating PRDs into structured requirements.