Name: data-contract
Author: asabocinski

Prompt file imported from asabocinski/bravo-edd (.codex/prompts/data-contract.md). Copyright stays with the author.

Data Contract Command

Author producer-consumer data contracts following the Open Data Contract Standard

Usage

/data-contract <description-or-file>

Examples

/data-contract "Contract between orders team and analytics"
/data-contract "SLA definition for customer dimension table"
/data-contract models/marts/mart_revenue.sql
/data-contract "Schema governance rules for the payments domain"

What This Command Does

Invokes the data-contracts-engineer agent
Analyzes your contract requirements or existing model
Loads KB patterns from data-quality and data-modeling domains
Generates:
- ODCS-compliant contract YAML
- Schema definitions with column-level contracts
- SLA specifications (freshness, completeness, accuracy)
- Producer-consumer agreement documentation
- Breaking change detection rules

Agent Delegation

Agent	Role
`data-contracts-engineer`	Primary — ODCS, SLAs, schema governance
`data-quality-analyst`	Escalation — quality rule enforcement
`schema-designer`	Escalation — schema evolution planning

KB Domains Used

data-quality — SLA patterns, quality metrics, observability
data-modeling — schema evolution, compatibility rules

Output

The agent generates ODCS contract YAML, SLA definitions, and governance documentation.

Install data-contract and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "prompt": "# Data Contract Command\n\n> Author producer-consumer data contracts following the Open Data Contract Standard\n\n## Usage\n\n```bash\n/data-contract <description-or-file>\n```\n\n## Examples\n\n```bash\n/data-contract \"Contract between orders team and analytics\"\n/data-contract \"SLA definition for customer dimension table\"\n/data-contract models/marts/mart_revenue.sql\n/data-contract \"Schema governance rules for the payments domain\"\n```\n\n---\n\n## What This Command Does\n\n1. Invokes the **data-contracts-engineer** agent\n2. Analyzes your contract requirements or existing model\n3. Loads KB patterns from `data-quality` and `data-modeling` domains\n4. Generates:\n - ODCS-compliant contract YAML\n - Schema definitions with column-level contracts\n - SLA specifications (freshness, completeness, accuracy)\n - Producer-consumer agreement documentation\n - Breaking change detection rules\n\n## Agent Delegation\n\n| Agent | Role |\n|-------|------|\n| `data-contracts-engineer` | Primary — ODCS, SLAs, schema governance |\n| `data-quality-analyst` | Escalation — quality rule enforcement |\n| `schema-designer` | Escalation — schema evolution planning |\n\n## KB Domains Used\n\n- `data-quality` — SLA patterns, quality metrics, observability\n- `data-modeling` — schema evolution, compatibility rules\n\n## Output\n\nThe agent generates ODCS contract YAML, SLA definitions, and governance documentation.", "variables": [], "notes": "Data contract authoring (ODCS) — delegates to data-contracts-engineer agent", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/asabocinski/bravo-edd", "path": ".codex/prompts/data-contract.md", "ref": "ae4c539580470e782ac67d2dc4a4eabe9fc68336", "url": "https://github.com/asabocinski/bravo-edd/blob/ae4c539580470e782ac67d2dc4a4eabe9fc68336/.codex/prompts/data-contract.md", "key": "asabocinski/bravo-edd/.codex/prompts/data-contract.md" } } }

data-contract

About

Data Contract Command

Usage

Examples

What This Command Does

Agent Delegation

KB Domains Used

Output

Install data-contract and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews