design-documents

Transform analyzed Oracle relational schemas into Cosmos DB NoSQL document models.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hariinfo/agentic-code-template --skill design-documents-hariinfo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-documents
Source: https://github.com/hariinfo/agentic-code-template/tree/main/.claude/skills/design-documents
Command: npx skills add https://github.com/hariinfo/agentic-code-template --skill design-documents-hariinfo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts an analyzed Oracle relational schema into a fully designed Cosmos DB NoSQL document model, enabling scalable, query-efficient migration from relational to document-based storage.

Core Features & Use Cases

  • Transforms tables, constraints, and PLSQL logic into denormalized document structures, containers, and access patterns.
  • Produces the complete design artifacts, including document-model.md with JSON schemas, column mappings, constraint migration, trigger mapping, denormalization registry, and full Cosmos DB configuration for migration.
  • Supports scoped inventories and flags dependency gaps and out-of-scope references to guide migration decisions.

Quick Start

Provide the Oracle schema analysis and inventory to generate the end-to-end Cosmos DB document model and all migration artifacts.

Frequently Asked Questions about design-documents

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

FAQPage Schema
How do I design Cosmos DB documents from an Oracle relational schema?

You can design Cosmos DB documents from an Oracle schema by transforming analyzed tables, constraints, and PLSQL logic into denormalized document structures, containers, and access patterns. This produces a complete NoSQL document model with JSON schemas and partition key mappings.

How do I map Oracle tables to Cosmos DB containers and partition keys?

Oracle tables are mapped to Cosmos DB containers by identifying partition keys and creating a denormalization registry. The transformation process evaluates table constraints and access patterns to determine optimal document structures and partition key strategies for the NoSQL model.

What is the best way to handle denormalization when migrating Oracle data to Cosmos DB?

Handling denormalization during Oracle to Cosmos DB migration involves creating a denormalization registry that transforms relational tables into embedded document structures. This process maps column constraints and PLSQL triggers to optimize query-efficient NoSQL access patterns.

Can I generate change-feed integration templates for an Oracle to Cosmos DB migration?

Yes, generating change-feed integration templates is part of the Cosmos DB document design process. The transformation includes trigger mapping and produces templates that support change-feed integration alongside container schemas, indexing policies, and throughput estimates.

Does this Oracle to Cosmos DB migration design support scoped schema inventories?

Yes, the design process accepts scoped inventories from analyzed Oracle schema outputs. It flags dependency gaps and out-of-scope references within the provided inventory to guide migration decisions and document assumptions.

How do I estimate throughput and indexing policy for migrated Cosmos DB containers?

Throughput estimates and indexing policies for migrated Cosmos DB containers are generated by analyzing the Oracle schema constraints and access patterns. The resulting design artifacts include full configuration details for container provisioning and query optimization.