update-drd

Merge new business requirements into Data Requirements Documents while preserving unchanged content.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually updating Data Requirements Documents (DRDs) is time-consuming, error-prone, and often leads to missing cross-section impacts, lost existing content, or incomplete version tracking when business requirements change. This Skill automates the entire DRD update workflow to ensure accuracy, traceability, and compliance with data engineering standards.

Core Features & Use Cases

  • Intelligent Change Merging: Reads existing DRDs and merges new stakeholder feedback, updated business rules, or new data sources while preserving all unchanged content.
  • Automated Versioning & Logging: Automatically increments document version numbers and adds detailed change log entries for full traceability of all modifications.
  • Ripple Effect Assessment: Evaluates how changes to one DRD section (e.g., new data source) impact other sections (e.g., data quality rules, consumer SLAs) to catch inconsistencies early.
  • Source Data Validation: Runs read-only database queries to verify that claimed new data sources exist, match expected schemas, and meet quality thresholds before updating the DRD.
  • Use Case: For example, if a healthcare stakeholder adds a new lab_results data source and requests a 1-second SLA for clinical reporting, the Skill will update the relevant DRD sections, verify the lab_results table exists in DuckDB, adjust data quality rules for new lab result fields, and ensure the SLA is reflected in consumer requirements.

Quick Start

Use the update-drd skill to revise your latest Data Requirements Document to add the new lab_results data source and update the clinical reporting consumer SLA to 1 second response time.

Frequently Asked Questions about update-drd

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

FAQPage Schema
How do I update a Data Requirements Document with new business requirements?

To update a Data Requirements Document, you can merge new business requirements while preserving unchanged content. The system automatically increments version numbers, maintains change logs, and assesses cross-section ripple effects to ensure data engineering compliance.

How does automated version tracking work for DRD revisions?

Automated version tracking for DRD revisions works by incrementing document version numbers and generating detailed change log entries. This captures stakeholder feedback, modified business rules, and newly discovered data sources for full traceability.

Can I validate source data schemas in DuckDB before updating a DRD?

Yes, you can validate source data before updating a DRD by running read-only database queries. This verifies that claimed new data sources exist in DuckDB, match expected schemas, and meet quality thresholds before finalizing the document.

What is the best way to assess ripple effects when adding new data sources to a DRD?

The best way to assess ripple effects when adding data sources to a DRD is to evaluate cross-section impacts automatically. This catches inconsistencies by checking how new sources affect data quality rules, consumer SLAs, and regulatory requirements.

Does updating DRDs with stakeholder feedback preserve existing regulatory requirements?

Yes, updating DRDs with stakeholder feedback preserves existing regulatory requirements and unchanged content. The system merges new feedback intelligently while ensuring compliance with DRD completeness standards throughout the revision workflow.

What happens if my DRD update fails completeness standards after merging changes?

If a DRD update fails completeness standards after merging changes, the workflow validates compliance before finalizing. It checks cross-section ripple effects and source data quality thresholds to prevent incomplete or inconsistent document versions.