data-contract-extractorlisted
Install: claude install-skill testland/qa-skills
# data-contract-extractor
## Overview
This skill formalizes the prose of a data PRD into a **data contract** -
the producer/consumer agreement on schema, freshness, volume, semantic
invariants, and ownership - that the QA test suite can mechanically
assert against, typically via the sibling skills in this plugin
(`dbt-testing`, `great-expectations`, `soda-checks`). "Data contract" is
practitioner-emergent terminology (Andrew Jones / Chad Sanderson), not
ISTQB-canonical; this skill cites industry-engineering sources.
## When to use
- A new data product (dbt model, table, file feed) is being scoped
and the team wants assertions before shipping.
- An existing data product has implicit assumptions consumers rely
on; the team is documenting them ahead of a refactor.
- A PRD or design doc references a dataset and the team needs the
schema / SLA pulled out into structured form.
- A data-quality engineer needs the contract as input to suite generation.
## What goes in a data contract
The five required sections, in order of authoring priority:
### 1. Schema
For each column:
| Field | Required | Notes |
|---------------|----------|-------|
| Name | yes | snake_case; matches the warehouse table. |
| Type | yes | Warehouse-native type (`VARCHAR`, `BIGINT`, `TIMESTAMP`, etc.). |
| Nullable | yes | `true` / `false` - the test suite's `not_null` decision. |
| PK | yes | `true` for primary-key column(s).