create-drd

Translate unstructured business inputs into formal Data Requirements Documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the ambiguity and misalignment between business stakeholders and data engineering teams by translating messy, unstructured business requests, stakeholder interviews, source system documentation, and data catalogs into formal, actionable Data Requirements Documents (DRDs) that serve as a single source of truth for data project requirements.

Core Features & Use Cases

  • Structured Requirements Elicitation: Uses a gap-based Q&A loop with targeted multiple-choice questions to fill missing or vague requirements across all DRD sections, ensuring no assumptions or incomplete information make it into the final document.
  • Live Source Data Verification: Queries actual source databases using read-only commands to verify table existence, row counts, column schemas, and data quality metrics, eliminating reliance on outdated or inaccurate document estimates.
  • Standardized DRD Generation: Produces business-friendly, consistent DRDs following a predefined Jinja2 template, with built-in validation, session memory for future reference, and automatic learning capture from user corrections.
  • Use Case: For example, a healthcare data team building a patient 360 search tool can use this Skill to take stakeholder interview notes, Synthea source system docs, and existing data catalogs to generate a complete DRD with all required sections including business context, data quality rules, consumer SLAs, and HIPAA compliance requirements.

Quick Start

Provide your business request, stakeholder interview notes, source system documentation, and data catalog files, then ask the AI to generate a complete, validated Data Requirements Document for your data project.

Frequently Asked Questions about create-drd

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

FAQPage Schema
How do I create a Data Requirements Document from stakeholder interviews and source system documentation?

To create a Data Requirements Document, you provide unstructured business inputs like stakeholder interview notes and source documentation, and the Skill translates them into formal, actionable DRDs using a standardized template.

What is the best way to align business stakeholders and data engineering teams on data project requirements?

Aligning business stakeholders and data engineering teams requires a formal Data Requirements Document. This Skill eliminates ambiguity by translating messy business requests into a single source of truth with built-in validation and traceability.

Can I verify source data schemas and row counts before generating data requirements?

You can verify source data schemas before generating data requirements. The Skill queries actual source databases using read-only commands to verify table existence, row counts, column schemas, and data quality metrics.

How does gap-based requirements elicitation work for data engineering projects?

Gap-based requirements elicitation works by using a targeted Q&A loop with multiple-choice questions. This fills missing or vague requirements across all DRD sections, ensuring no assumptions or incomplete information make it into the final document.

Do I need existing data catalogs to generate a DRD for a new data product?

You do not strictly need existing data catalogs to generate a DRD, but providing them alongside stakeholder interview notes and source system documentation improves the accuracy of the structured requirements document.

What limitations exist when using automated DRD generation for healthcare data integration projects?

Automated DRD generation for healthcare data integration relies on the accuracy of provided business inputs. While it captures compliance requirements like HIPAA, it cannot independently validate business logic outside of read-only database verification.