evaluator-contract-review

Review sprint proposals to produce contracts with acceptance criteria.

28|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/thompson0012/agents-stack --skill evaluator-contract-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evaluator-contract-review
Source: https://github.com/thompson0012/agents-stack/tree/main/templates/.agents/skills/using-agents-stack/evaluator-contract-review
Command: npx skills add https://github.com/thompson0012/agents-stack --skill evaluator-contract-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial review ensures sprint proposals are thoroughly challenged to reveal gaps and produce a clear, enforceable contract.

Core Features & Use Cases

  • Adversarially critiquing sprint proposals to identify gaps, risks, and ambiguities.
  • Producing precise revision feedback and a durable contract that is testable and auditable.
  • Verifying boundaries, acceptance criteria, and observed evidence using stable artifacts.

Quick Start

Provide the sprint proposal and related inputs, and let evaluator-contract-review generate a contract or actionable revision notes.

Frequently Asked Questions about evaluator-contract-review

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

FAQPage Schema
What is adversarial review for sprint contracts?

Adversarial review challenges sprint proposals to uncover gaps, risks, and ambiguities, producing a precise, enforceable contract with testable acceptance criteria and verifiable boundaries.

How do I create acceptance criteria for a sprint proposal?

Define acceptance criteria using AC-### IDs, including before, action, and after verifications. Adversarial review ensures these criteria are explicit, testable, and auditable within the final contract.

Can I use this for backlog management without an existing sprint proposal?

No, adversarial contract review requires an existing sprint proposal file at .harness/<workstream-id>/sprint_proposal.md and related reference docs to function properly.

What's the best way to handle revision notes from a sprint proposal evaluation?

When gaps are found during proposal evaluation, the process outputs structured revision notes identifying specific deficiencies, allowing you to refine the proposal before generating a final contract.

Does contract review work without explicit boundaries in the proposal?

No, explicit boundaries are required. Adversarial review validates that sprint proposals contain defined boundaries, AC-### ID acceptance criteria, and before/action/after verifications before producing a contract.

Why does my sprint contract need before, action, and after verifications?

Before, action, and after verifications ensure observed evidence is testable and auditable. They provide stable artifacts that validate acceptance criteria and confirm contract compliance.