ba-system-overview-datamodel

Generate a 5-section system overview and PRD from data model, applications, and actors.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps Business Analysts convert data models, applications, and actor lists into a single, consumable system overview and PRD-style documentation, reducing manual drafting time and ensuring consistency across artifacts.

Core Features & Use Cases

  • Generate a 5-section system overview document from the data model, apps, and actors.
  • Link entities to applications and actors, and surface the data dictionary for quick reference.
  • Produce a ground-truth PRD with defined inputs and clear dependencies for brownfield projects.

Quick Start

Generate the PRD-style ba-system-overview-datamodel in docs-BA/PRD using the provided Data Model, Applications, and Actors.

Frequently Asked Questions about ba-system-overview-datamodel

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

FAQPage Schema
How do I generate a PRD from an existing data model for a brownfield project?

To generate a PRD from a data model for a brownfield project, you need to input your database tables, fields, application list, and actor roles to automatically produce a 5-section system overview document with cross-references.

What is the best way to map application and actor relationships to data dictionary tables?

Mapping application and actor relationships to data dictionary tables involves linking your provided actor roles and application lists directly to specific database entities, creating a coherent system overview that surfaces data relationships.

What inputs do I need to create a data-model-linked system overview document?

To create a data-model-linked system overview document, you must provide three inputs: a data model containing tables and fields, a list of applications, and defined actor roles to map the app-table-column relationships.

Can I use this approach to document app-table-column relationships for business analysts?

Yes, business analysts can use this approach to document app-table-column relationships by transforming data models and actor lists into a single consumable PRD-style artifact, ensuring consistency and reducing manual drafting time.

Does generating a data-model-linked PRD work for brownfield system overviews without external dependencies?

Generating a data-model-linked PRD for brownfield system overviews works without external dependencies, relying solely on your provided data model, application list, and actor roles to produce the structured documentation.