schema-spec

What problem does it solve?

Data teams often struggle with undocumented schema elements, inconsistent field definitions, and uncontrolled schema changes that ripple through downstream analytics and data products. This Skill provides a repeatable blueprint to document headers, data types, nullability, keys, and evolution rules to establish a clear data contract between producers and consumers.

Core Features & Use Cases

• Structured schema headers: Define a standardized header section (Schema, Domain, Owner, Type, Storage, Created, Version) for every schema artifact.
• Field documentation: Describe each field with precise types, nullability, default values, and business meaning; include enums and constraints.
• Keys, indexes, and constraints: Capture primary/foreign keys, unique constraints, and indexes to enable correct query planning and data integrity.
• Evolution and governance: State evolution policies for adding/removing columns, renaming fields, and deprecations to minimize breaking changes.

Quick Start

Write a new schema spec by specifying the header details and detailing each field's type, nullability, and purpose.