skills.rest
RDEWAI
RDEWAIOFFICIAL
Explore all skills by this author →
GitHub

validate-lld

Validate Low-Level Design documents for completeness and quality standards.

5|1|Updated Sep 23, 2025
Search Tags:#data-engineering#unity-catalog#design-audit#technical-lead#low-level-design#spark-expectations#lld-validation
One-click install
npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill validate-lld
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-lld
Source: https://github.com/RDEWAI/Redefining-DataEngineering-With-AI/tree/main/chapter-6/technical-lead-plugin/skills/validate-lld
Command: npx skills add https://github.com/RDEWAI/Redefining-DataEngineering-With-AI --skill validate-lld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Incomplete or non-compliant Low-Level Design (LLD) documents cause downstream development delays, rework, and misalignment with upstream requirements and runtime contracts, leading to wasted effort and broken pipeline deployments.

Core Features & Use Cases

  • Completeness Validation: Checks all 14 required LLD sections are present and populated with meaningful content.
  • Quality Rule Enforcement: Validates critical contracts like Bronze runner Unity Catalog wiring, local_executor_mode declarations, spark-expectations version pinning, and upstream artifact references.
  • Severity-Ranked Reporting: Flags issues as CRITICAL (blocks development), WARNING (needs attention), or INFO (suggestions) with actionable fix suggestions, and auto-fixes resolvable CRITICAL issues.
  • Use Case: A Technical Lead can run this skill before handing off an LLD to the development team to ensure no missing requirements, contract violations, or structural gaps that would cause implementation failures.

Quick Start

Use the validate-lld skill to audit the LLD file outputs/lld/v1/LLD-patient-360.md for completeness and quality issues before handing it off to the development team.

Frequently Asked Questions about validate-lld

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

FAQPage Schema
How do I validate a Low-Level Design document before development handoff?▼

Validating a Low-Level Design (LLD) document before development handoff involves checking all 14 required sections for completeness, verifying critical contracts like Unity Catalog Bronze wiring and spark-expectations version pinning, and resolving structural gaps to prevent downstream rework.

What is LLD completeness validation for data engineering pipelines?▼

LLD completeness validation is an audit process that verifies mandatory design sections, DAG specifications, and configuration schemas are present and populated to ensure technical leads block non-compliant pipeline designs before implementation begins.

How do I enforce local_executor_mode declarations and Unity Catalog Bronze wiring in an LLD?▼

Enforcing local_executor_mode declarations and Unity Catalog Bronze wiring requires applying quality rules to the LLD document that flag missing contract definitions as CRITICAL issues, ensuring pipeline runtime expectations are explicitly stated before development.

Can I automate design audits for upstream artifact references and DAG specifications?▼

Automating design audits for upstream artifact references and DAG specifications is possible by running a validation script that checks for section presence and enforces subsection structure, automatically generating severity-ranked reports for missing requirements.

What issues are flagged when validating spark-expectations version pinning in a design document?▼

Validating spark-expectations version pinning flags issues using severity ranks: CRITICAL issues block development, WARNING issues need attention, and INFO issues provide suggestions, with actionable fix recommendations generated for each detected contract violation.

Why does missing subsection structure in an LLD cause development rework?▼

Missing subsection structure in an LLD causes development rework because it indicates incomplete performance optimization plans, ambiguous Bronze runner contracts, and unvalidated upstream dependencies that lead to broken pipeline deployments and wasted engineering effort.

Related Skills

Explore More Software Engineering Skills→
RDEWAIRDEWAI
5

update-lld

Merge upstream artifacts into Low-Level Design documents while preserving unchanged content.

Official
Advanced
RDEWAIRDEWAI
5

create-ingestion

Generate config-driven Bronze ingestion code for Spark and Delta Lake pipelines.

Official
Advanced
RDEWAIRDEWAI
5

create-integration-test

Generates integration tests for Docker-based apps with CI/CD pipelines and automated workflows.

Official
Advanced
sjinkssjinks

security-review-owasp-virtual-patching

Identify virtual patching security review gaps in code, configuration, architecture, and operations.

Community
Advanced