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.