evaluator-review-contract

Stars13

Forks1

UpdatedApril 5, 2026 at 16:17

Internal Auto-Harness evaluator skill for sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

redker56

redker56/auto-harness

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

3 files

SKILL.md

readonly

name	evaluator-review-contract
description	Internal Auto-Harness evaluator skill for sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.
user-invocable	false

Evaluator Review Contract

This skill governs Evaluator review mode.

At the start of this action, read these harness artifacts from the project:

.harness/status.md
.harness/intake.md
.harness/spec.md
.harness/design-direction.md
.harness/contracts/sprint-XX-contract.md
.harness/contracts/sprint-XX-review.md when revising an existing review.

Then inspect the current project implementation relevant to this action:

Read the current source files, routes, components, services, tests, and config that determine whether the proposed sprint contract is feasible and respects locked decisions.
Use the codebase to judge feasibility, integration points, and constraint compliance before implementation begins.

Then read these skill references:

references/templates/sprint-contract.md
references/protocols/file-ownership.md

Follow these rules:

Review the sprint contract before implementation begins.
Fail the review when scope, testability, verification readiness, or locked decisions are violated.
Judge the contract against the written artifacts and the current implementation, not Generator intent.
If feasibility or verification cannot be established from the current contract plus the existing codebase, fail conservatively and say why.
Cite exact files, boundaries, runtime assumptions, or locked decisions when a hard blocker or revision request is raised.
Write only the sprint review artifact.
Do not modify application source code or generator-owned artifacts.

More from this repository

same repository

evaluator-review-contract-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.

2026-05-0213

evaluator-write-final-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel final QA report aggregation. Use only inside the Evaluator subagent during evaluator_final_parallel.

2026-05-0213

evaluator-write-qa-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint QA and QA report writing. Use only inside the Evaluator subagent during evaluator_qa_parallel.

2026-05-0213

evaluator-write-retest-parallel

redker56/auto-harness

Internal Auto-Harness evaluator skill for parallel sprint retest and retest report writing. Use only inside the Evaluator subagent during evaluator_retest_parallel.

2026-05-0213

generator-build-integrator

redker56/auto-harness

Internal Auto-Harness generator skill for worktree-merge build integration. Use only inside the parallel Generator integrator during build mode.

2026-05-0213

generator-build-worker

redker56/auto-harness

Internal Auto-Harness generator skill for one build dependency-graph node in a dedicated worktree.

2026-05-0213

name	evaluator-review-contract
description	Internal Auto-Harness evaluator skill for sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.
user-invocable	false

Evaluator Review Contract

This skill governs Evaluator review mode.

At the start of this action, read these harness artifacts from the project:

.harness/status.md
.harness/intake.md
.harness/spec.md
.harness/design-direction.md
.harness/contracts/sprint-XX-contract.md
.harness/contracts/sprint-XX-review.md when revising an existing review.

Then inspect the current project implementation relevant to this action:

Read the current source files, routes, components, services, tests, and config that determine whether the proposed sprint contract is feasible and respects locked decisions.
Use the codebase to judge feasibility, integration points, and constraint compliance before implementation begins.

Then read these skill references:

references/templates/sprint-contract.md
references/protocols/file-ownership.md

Follow these rules:

Review the sprint contract before implementation begins.
Fail the review when scope, testability, verification readiness, or locked decisions are violated.
Judge the contract against the written artifacts and the current implementation, not Generator intent.
If feasibility or verification cannot be established from the current contract plus the existing codebase, fail conservatively and say why.
Cite exact files, boundaries, runtime assumptions, or locked decisions when a hard blocker or revision request is raised.
Write only the sprint review artifact.
Do not modify application source code or generator-owned artifacts.