contract-manager

Review plans, bug fixes, and designs to produce a Contract Review Document.

6|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/anotherben/claude-harness --skill contract-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contract-manager
Source: https://github.com/anotherben/claude-harness/tree/main/skills/contract-manager
Command: npx skills add https://github.com/anotherben/claude-harness --skill contract-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews plans, bug fixes, and feature designs to produce a Contract Review Document before any implementation begins. The contract must be so precise that any model at any level can implement it mechanically — no interpretation, no assumptions, just applying code to files.

Core Features & Use Cases

  • Two modes: Contract Review (pre-implementation) and Contract Verification (post-implementation) — enabling both specification and verification in one workflow.
  • Live verifications and documentation: verify facts against source documents, code, and live systems, and capture results in a formal contract document.
  • Standardized contract lifecycle: trigger, document, verify, and rollback guidance to reduce ambiguity and drift across projects.

Quick Start

Start with a contract review when plans or designs are ready, then perform contract verification after implementation.

Frequently Asked Questions about contract-manager

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

FAQPage Schema
How do I formalize software specifications to prevent ambiguity before implementation?

Contract review identifies and formalizes every specification before coding begins, producing a Contract Review Document so precise any model can implement it mechanically without interpretation.

When do I need to run contract verification on my project?

Contract verification runs post-implementation to verify facts against source documents, code, and live systems, capturing results in a formal contract document with explicit postconditions.

How do I enforce a standardized contract lifecycle for plans and bug fixes?

Apply the workflow to plans, bug fixes, and designs to trigger, document, verify, and rollback contracts, reducing ambiguity and drift across the entire project lifecycle.

Can I use contract review for both feature designs and bug fixes?

Yes, contract review works for plans, bug fixes, and feature designs, ensuring all specifications are perfectly formalized before any implementation begins.

What's the best way to verify implementation against original specifications?

Use the contract verification mode to perform live verifications against source documents and code, capturing traceable artifacts and postconditions in a single contract document.

Why does my software project suffer from specification drift across the lifecycle?

Specification drift occurs without a standardized contract lifecycle; formalizing contracts with live verifications and traceable artifacts prevents ambiguity across projects.