update-dms

Merge schema changes and SCD updates into DMS documents with versioning.

5|1|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill update-dms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-dms
Source: https://github.com/RDEWAI/Redefining-DataEngineering-With-AI/tree/main/chapter-6/data-modeler-plugin/skills/update-dms
Command: npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill update-dms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually updating large, complex Data Model Specification (DMS) documents is error-prone, risks losing existing valid content, breaks traceability to High-Level Design (HLD) and Data Requirements Documents (DRD), and requires tedious manual version tracking and change log management.

Core Features & Use Cases

  • Safe Schema Updates: Merges schema changes, SCD strategy revisions, HLD alignment adjustments, and naming convention updates into existing DMS documents while preserving all unchanged content and enforcing cross-section consistency.
  • Automated Versioning & Validation: Automatically increments version numbers, adds change log entries, validates YAML schema block syntax, verifies HLD traceability citations, and runs post-update validation to catch errors before handoff.
  • Use Case: For example, if your HLD adds a new silver layer clinical_patients table and updates SCD requirements for the dim_patient dimension, use this skill to update the DMS to include the new table schema, adjust SCD type definitions, update the traceability matrix, and bump the version number without breaking existing bronze or gold layer definitions.

Quick Start

Use the update-dms skill to revise your latest data model specification document to add SCD Type 2 tracking for the provider specialty dimension and align all gold layer schemas with the updated HLD layer specs.

Frequently Asked Questions about update-dms

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

FAQPage Schema
How do I update a Data Model Specification document without losing existing valid content?

Validating YAML schema block syntax is essential when revising a data model specification to catch structural errors before handoff. Post-update validation verifies that schema blocks are syntactically correct and cross-section consistency is maintained.

What is the best way to maintain HLD traceability when changing data model schemas?

Maintaining HLD traceability during schema changes requires verifying traceability citations within the data model specification against High-Level Design standards. Automated enforcement verifies that all schema revisions align with HLD and Data Requirements Documents.

How do I automate version incrementing and change log creation for data modeling documents?

Automating version incrementing and change log creation for data modeling documents requires a revision process that automatically bumps version numbers and adds change log entries. This tracks schema modifications and SCD strategy updates with full traceability.

Can I merge SCD strategy updates into an existing data model specification without breaking other layers?

You can merge SCD strategy updates into an existing data model specification without breaking other layers by using a safe merge process. This adjusts SCD type definitions for specific dimensions while preserving bronze, silver, or gold layer definitions.

When should I not manually update a data model specification?

You should not manually update a data model specification when dealing with large, complex documents with extensive HLD traceability matrices. Manual updates risk breaking traceability, losing valid content, and introducing errors in version tracking.