ba-system-overview-datamodel

Generate a 5-section PRD and data model document from input data models, app inventories, and actor roles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill synthesizes a system overview from a Data Model, the list of apps, and actor roles, enabling consistent AS-IS documentation and PRD generation.

Core Features & Use Cases

  • Generate a Data Model document in docs-BA/Data Model from inputs (SQL/Prisma/DDL) when not present in repo.
  • Produce a 5-section PRD overview (1. Tổng quan; 2. Danh sách đối tượng sử dụng; 3. Danh sách ứng dụng; 4. Quy trình nghiệp vụ; 5. Danh sách chức năng theo ứng dụng).
  • Map entities to applications and actors to facilitate brownfield mapping and data dictionary extraction.

Quick Start

Provide a data model input plus lists of applications and users to generate both the data model document and the PRD.

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 for an existing brownfield system?

To generate a PRD for a brownfield system, map existing entities to applications and actors. This produces a 5-section PRD covering overview, users, apps, business processes, and app functions.

How do I create a data model document from SQL or Prisma schema?

You can create a data model document from SQL, Prisma, or DDL inputs. The system transforms these schema definitions into a cohesive data model document with relationship diagrams and governance notes.

What is entity-application mapping and when do I need it?

Entity-application mapping connects data model entities to their corresponding applications and actors. It is needed for brownfield documentation to extract data dictionaries and facilitate system overview synthesis.

Can I generate system documentation without an existing data model in the repo?

Yes, you can generate documentation without an existing repo data model. Simply provide SQL, Prisma, or DDL inputs along with application and user lists to synthesize the data model document and PRD.

What's the best way to map actor roles to applications for AS-IS documentation?

The best way to map actor roles for AS-IS documentation is to input application inventories and user lists alongside the data model. This synthesizes a cohesive system overview with actor-to-application mapping.

Does this system overview tool work with DDL inputs for data dictionary extraction?

Yes, the system overview tool works with DDL inputs for data dictionary extraction. It accepts DDL, SQL, or Prisma formats to map entities to applications and generate governance notes.