validate-drd

Validate Data Requirements Documents for completeness and quality gaps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually reviewing Data Requirements Documents is error-prone and time-consuming, often missing critical gaps like incomplete sections, undefined SLAs, or missing regulatory compliance details that cause rework and delays in data engineering projects.

Core Features & Use Cases

  • Automated Completeness Checks: Validates all 9 required DRD sections, version metadata, source systems, and consumer requirements are present and non-empty.
  • Quality & Compliance Audits: Flags vague language, missing SLAs, undefined tolerance thresholds, and incomplete regulatory subsections with severity-ranked findings (CRITICAL/WARNING/INFO) and actionable fix suggestions.
  • Auto-Remediation: Automatically fixes critical structural issues like missing sections or empty metadata, and prompts for user input on business-specific gaps before finalizing the report. Use case: A business analyst can validate a patient data DRD before handing it to the data engineering team to ensure all regulatory and quality requirements are captured upfront, avoiding costly rework later.

Quick Start

Use the validate-drd skill to run a full completeness and quality validation on the Data Requirements Document located at 'outputs/drd/patient-360.md'.

Frequently Asked Questions about validate-drd

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

FAQPage Schema
How do I validate a Data Requirements Document before handing it to data engineering?

To validate a Data Requirements Document, you can run automated completeness and quality checks against required sections, metadata, and SLAs. This process identifies gaps and outputs a severity-ranked report with actionable fixes before engineering work begins.

What is DRD validation and how does it catch requirements gaps?

DRD validation is the automated process of auditing Data Requirements Documents for completeness and quality. It checks required sections, flags vague language and missing regulatory details, and assigns severity rankings to catch gaps early.

Can I check multiple DRD files for missing SLAs and compliance details at once?

Yes, you can check multiple DRD files at once using batch validation. This feature processes several Data Requirements Documents simultaneously, identifying missing SLAs, undefined tolerance thresholds, and incomplete regulatory subsections across the entire batch.

Does the requirements check support auto-remediation for missing sections?

Yes, the requirements check supports auto-remediation by automatically fixing critical structural issues like missing sections or empty metadata. It prompts for user input on business-specific gaps before finalizing the validation report.

What is the best way to audit business analysis requirements for data quality?

The best way to audit business analysis requirements is to apply an automated quality audit that flags vague language and missing SLAs. This approach outputs severity-ranked findings with actionable fix suggestions to ensure data-centric project requirements are complete.

What format does the DRD file need to be in for the validation script to process it?

The DRD file needs to be in Markdown format for the validation script to process it. The tool requires a Markdown file as input to parse the sections, metadata, and requirements, and outputs a severity-ranked validation report.