contract-steward

Name: contract-steward
Availability: InStock
Author: Vel-Labs

Enforce canonical contract authority with HumanReviewCheckpoint gates and changelog updates.

Updated Apr 26, 2026

Search Tags:#validation #auditing #governance #lifecycle #contract #change-management #human-review

Ready to run

npx skills add https://github.com/Vel-Labs/ClearIntent --skill contract-steward

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contract-steward
Source: https://github.com/Vel-Labs/ClearIntent/tree/main/skills/contract-steward
Command: npx skills add https://github.com/Vel-Labs/ClearIntent --skill contract-steward

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps canonical authority in contract governance as the single source of truth, preventing drift into tests, docs, or implementation packages.

Core Features & Use Cases

Enforces governance boundaries by prioritizing contracts and lifecycle decisions as the authority.
Guides updates to docs, schemas, examples, and validation rules when canonical truth changes.
Provides a HumanReviewCheckpoint gate to ensure human oversight before changes are finalized.

Quick Start

Follow the contract stewardship workflow to verify any proposed change against the canonical contracts before publication.

Frequently Asked Questions about contract-steward

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

FAQPage Schema

How do I prevent contract governance drift when updating schemas and validation rules?▼

To prevent contract governance drift, enforce canonical authority by prioritizing contracts as the single source of truth. This ensures updates to schemas and validation rules align with the established canonical contracts before publication.

What is a HumanReviewCheckpoint gate in contract change management?▼

A HumanReviewCheckpoint gate is a workflow mechanism that ensures human oversight before finalizing contract changes. It requires manual review and changelog updates, preventing unauthorized or unreviewed modifications to canonical authority.

How do I propagate canonical contract truth changes to documentation and tests?▼

Propagate canonical contract changes by applying a contract stewardship workflow that verifies proposed updates against canonical contracts. This guides synchronized updates to documentation, examples, and tests to prevent drift.

When do I need canonical authority enforcement for smart contract lifecycles?▼

Canonical authority enforcement is needed when applying updates across smart contract lifecycles, schemas, and validation rules. It preserves governance boundaries and ensures that contract decisions remain the primary authority.

Does contract stewardship work for managing changes across multiple contract schemas?▼

Yes, contract stewardship applies to updates across contracts, schemas, lifecycles, and validation rules. It enforces canonical authority boundaries to ensure all schema changes are validated against the governing contract.

Why does my contract documentation drift from the actual validation rules?▼

Documentation drifts from validation rules when canonical authority is not enforced as the single source of truth. Without a contract stewardship workflow, updates to rules bypass documentation synchronization and human review gates.