create-hld

Generate traceable High-Level Design documents from approved 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-hld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-hld
Source: https://github.com/RDEWAI/Redefining-DataEngineering-With-AI/tree/main/chapter-6/architect-plugin/skills/create-hld
Command: npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill create-hld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually translating approved Data Requirements Documents (DRDs) into consistent, traceable High-Level Design (HLD) documents for data engineering projects is time-consuming, error-prone, and often misses critical traceability to original requirements or alignment with team capabilities and infrastructure constraints.

Core Features & Use Cases

  • DRD Traceability Enforcement: Automatically links every design decision in the HLD to specific sections of the source DRD, ensuring no requirements are missed or unaddressed.
  • Built-in Validation Gates: Blocks HLD generation if upstream DRDs are not approved or source data volumes are unverified, preventing invalid or mis-sized designs.
  • Structured Elicitation Workflow: Guides architects through targeted Q&A to fill design gaps, eliminating vague or incomplete design choices.
  • Use Case: A data architect building a patient data pipeline can use this skill to generate a compliant HLD in hours instead of days, with all design decisions justified and aligned to DRD SLAs, team skills, and infrastructure limits.

Quick Start

Provide your approved DRD and architect input documents to the create-hld skill to generate a complete, compliant High-Level Design document.

Frequently Asked Questions about create-hld

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

FAQPage Schema
How do I generate a High-Level Design from a Data Requirements Document?

To generate a High-Level Design (HLD) from a Data Requirements Document (DRD), you provide the approved DRD and architect input artifacts to automate pattern selection, technology decisions, and capacity planning into a structured, traceable design specification.

Why does HLD generation require approved DRDs and verified source data volumes?

HLD generation enforces built-in validation gates that block processing if upstream DRDs are unapproved or source data volumes are unverified, preventing the creation of invalid or mis-sized technical design specifications.

What is DRD traceability in data architecture design?

DRD traceability is the automated linking of every design decision in a High-Level Design document directly to specific sections of the source Data Requirements Document, ensuring all business requirements are addressed and validated.

Can I use automated HLD generation for data engineering capacity planning?

Yes, automated HLD generation handles capacity planning by validating source data volumes and aligning data layer strategies with infrastructure constraints and team capabilities during the technical design specification process.

How do I fill design gaps when translating data requirements into technical specifications?

You can fill design gaps during HLD generation by using a structured elicitation workflow that guides data architects through targeted Q&A to clarify vague or incomplete design choices before finalizing the document.

What is the best way to align data pipeline architecture with team capabilities and infrastructure limits?

The best way to align data pipeline architecture with team capabilities and infrastructure limits is to generate a compliant HLD that enforces DRD traceability and validates source data volumes against existing infrastructure constraints.