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'.