Data Contract Skill

Most data outages are a producer changing a column without telling anyone downstream. A data contract fixes that: it's an explicit, versioned agreement on the schema, semantics, and quality guarantees of a dataset/event/stream, with an owner and a breaking-change policy. This skill writes one, so producers and consumers share a single source of truth and changes can't silently break pipelines.

Required Inputs

Ask for these only if they aren't already provided:

• The data asset — the table, event, topic, or API, and what it represents.
• Producer & consumers — who owns it, who depends on it.
• Schema — fields, types, and which are required; the semantics of the tricky ones.
• Quality expectations — freshness (how current), completeness, valid ranges, uniqueness.

Output Format