build-database

Generate a database diagram HTML from approved architecture and scope-of-work documents.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/aoecosystem/project-foundations --skill build-database
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-database
Source: https://github.com/aoecosystem/project-foundations/tree/main/.cursor/skills/build-database
Command: npx skills add https://github.com/aoecosystem/project-foundations --skill build-database

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts a database diagram from the approved Architecture and SoW, ensuring a consistent, auditable artifact that can be used for planning and communication.

Core Features & Use Cases

  • Reads scope-of-work and system-architecture HTML to extract entities, relationships, constraints, and service boundaries.
  • Applies architecture style guidance to produce a compliant, multi-service database diagram.
  • Writes the final diagram to project-diagrams/<slug>-database-diagram.html and advances the stage to DATABASE_DRAFT.

Quick Start

Run /build-database after architecture approval to generate and save the database diagram.

Frequently Asked Questions about build-database

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

FAQPage Schema
How do I generate a database diagram from an approved system architecture?

To generate a database diagram, the system reads approved scope-of-work and system-architecture HTML files to extract entities and relationships, applying architecture style guidance to output a compliant multi-service visualization.

When do I need to create a database diagram for my project?

You need a database diagram when your architecture is approved and your project requires visualizing database schema details across multiple services for clear planning and stakeholder communication.

Can I draft a database schema if my architecture is not yet approved?

No, drafting a database diagram requires the session state to enforce the ARCHITECTURE_APPROVED stage, ensuring the schema is generated only from validated scope-of-work and system-architecture inputs.

What is the best way to visualize database schema boundaries across services?

The best way to visualize multi-service schema boundaries is to extract service boundaries and constraints from approved architecture HTML, generating a compliant database diagram that maps relationships across services.

How do I save a generated database diagram for project documentation?

The generated database diagram is saved directly as an HTML file to the project-diagrams directory, creating an auditable artifact that updates the workflow stage to DATABASE_DRAFT upon completion.