Internal Auto-Harness evaluator skill for parallel sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.
Scanned 5/27/2026
Install via CLI
openskills install redker56/auto-harness---
name: evaluator-review-contract-parallel
description: Internal Auto-Harness evaluator skill for parallel sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.
user-invocable: false
---
# Evaluator Review Contract Parallel
This skill governs Evaluator **review mode**.
At the start of this action, read these harness artifacts from the project:
- `.harness-parallel/status.md`
- `.harness-parallel/intake.md`
- `.harness-parallel/spec.md`
- `.harness-parallel/design-direction.md`
- `.harness-parallel/contracts/sprint-XX-contract.md`
- `.harness-parallel/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.
- Review both `Parallel Workstreams` and `Dependency Graph JSON`.
- Fail the review if two nodes overlap on owned files, if dependency edges are missing for coupled modules, or if behavior coverage is incomplete.
- Fail the review if the graph is missing, malformed, cyclic, or references unknown behavior rows.
- 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.
No comments yet. Be the first to comment!