des-bronze-layer-design

Designs a Bronze layer specification for raw storage, metadata, retention, and schema drift.

2|Updated May 20, 2026
One-click install
npx skills add https://github.com/DKSang/DES-SKILL --skill des-bronze-layer-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: des-bronze-layer-design
Source: https://github.com/DKSang/DES-SKILL/tree/main/skills/des-bronze-layer-design
Command: npx skills add https://github.com/DKSang/DES-SKILL --skill des-bronze-layer-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of getting a reliable Bronze Layer Specification that preserves raw/near-raw source fidelity, ingestion evidence, audit/lineage metadata, schema-drift handling, and replay/quarantine behavior so downstream Silver/Gold work can be safe and recoverable.

Core Features & Use Cases

  • Bronze layer specification for raw evidence storage: Defines what gets stored from each ingestion source and how it is organized for traceability and recovery.
  • Ingestion evidence, audit, and lineage readiness: Specifies mandatory metadata columns, ingestion audit fields, and source-to-Bronze traceability expectations.
  • Operational safety for change and failure: Designs schema drift policy, replay/backfill support, idempotency/deduplication boundaries, and quarantine/rejected data handling without applying business conformance.

Quick Start

Use des-bronze-layer-design to create or update _des-output/planning-artifacts/09-bronze-layer-specification.md based on your Phase 08 ingestion specification and Phase 08-to-09 handoff.

Frequently Asked Questions about des-bronze-layer-design

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

FAQPage Schema
What is a bronze layer in data engineering and why do I need raw evidence storage?

A bronze layer is a raw or near-raw storage boundary in data pipelines that preserves source fidelity, ingestion evidence, and audit metadata. You need it to ensure downstream transformations are safe, traceable, and recoverable.

How do I design a bronze layer specification that handles schema drift and replay backfills?

You design a bronze layer specification by defining policies for schema drift, idempotency, deduplication boundaries, and replay/backfill support. This ensures operational safety and preserves source evidence without applying business conformance.

Do I need an ingestion specification before I can design bronze layer quarantine handling?

Yes, you need a Phase 08 ingestion specification and handoff available. Bronze layer design requires configured input artifacts detailing ingestion patterns and upstream handoffs to properly define quarantine and rejected data behaviors.

Can I implement Silver or Gold business logic while designing the bronze raw evidence layer?

No, bronze layer design strictly focuses on raw evidence storage, metadata, retention, and access control. It does not implement pipeline logic or downstream Silver and Gold business transformations.

What's the best way to ensure data lineage and audit readiness in a bronze layer?

The best way to ensure lineage and audit readiness is to specify mandatory metadata columns and source-to-bronze traceability expectations. This approach captures ingestion evidence required for downstream transformation safety.