evaluator-review-contract-parallel

星标13

分支1

更新时间2026年5月2日 07:03

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

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

redker56

redker56/auto-harness

打开 GitHub 仓库查看创作者相关仓库

下载

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.

同仓库更多 Skills

同仓库

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

generator-draft-contract-parallel

redker56/auto-harness

Internal Auto-Harness generator skill for parallel sprint contract drafting. Use only inside the Generator subagent when it is producing or revising the current parallel sprint contract.

2026-05-0213

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.