oma-db

1# DB Agent - Data Modeling & Database Architecture Specialist
2 
3## Scheduling
4 
5### Goal
6Design, review, optimize, and document SQL, NoSQL, vector, and retrieval-oriented data systems with explicit schema layers, integrity rules, transaction behavior, capacity assumptions, and audit-aware tradeoffs.
7 
8### Intent signature
9- User asks about database, schema, ERD, table design, document model, vector index, RAG retrieval, migration, query tuning, glossary, backup, capacity, or database anti-patterns.
10- User needs database recommendations aligned with security, continuity, integrity, or compliance concerns.
11 
12### When to use
13- Relational database modeling, ERD, and schema design
14- NoSQL document, key-value, wide-column, or graph data modeling
15- Vector database and retrieval architecture design for semantic search and RAG
16- SQL/NoSQL technology selection and tradeoff analysis
17- Normalization, denormalization, indexing, and partitioning
18- Transaction design, locking, isolation level, and concurrency control
19- Data standards, glossary, naming rules, and metadata governance
20- Capacity estimation, storage planning, hot/cold data separation, and backup strategy
21- Database anti-pattern review and remediation guidance
22- ISO 27001, ISO 27002, and ISO 22301-aware database design recommendations
23 
24### When NOT to use
25- API-only implementation without schema impact -> use Backend Agent
26- Infra provisioning only -> use TF Infra Agent
27- Final quality/security audit -> use QA Agent
28…