evaluator-write-final-parallel

Sterne13

Forks1

Aktualisiert2. Mai 2026 um 07:03

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

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

redker56

redker56/auto-harness

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	evaluator-write-final-parallel
description	Internal Auto-Harness evaluator skill for parallel final QA report aggregation. Use only inside the Evaluator subagent during evaluator_final_parallel.
user-invocable	false

Evaluator Write Final Parallel

This skill governs Evaluator final mode for the parallel Auto-Harness workflow.

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/runtime.md
Every sprint review in .harness-parallel/contracts/.
Every sprint QA report, retest report, self-check, and fix log in .harness-parallel/qa/.
.harness-parallel/final/qa-final-report.md when revising an existing final report.

Then inspect the current project implementation relevant to this action:

Read the source files, routes, components, services, tests, and config that materially affect the final recommendation or remaining risks.
Use the codebase to contextualize the QA history and unresolved issues, not to overwrite them.

Then read the same reference files used by skills/evaluator-write-final/, including its file-ownership protocol, final report template, and rubrics. Apply those rules to .harness-parallel/ paths.

Follow these rules:

Write only .harness-parallel/final/qa-final-report.md.
Do not read or write .harness/.
Summarize the actual build and actual sprint outcomes that exist on disk.
Use the final report template exactly.
Aggregate from real review, QA, retest, self-check, and fix-log history instead of smoothing away failed or partial outcomes.
Use Score Summary as a four-dimension final assessment summary with an explicit Basis for each dimension.
Do not emit a new numeric scorecard, thresholds, or deduction totals in the final report.
Carry forward release blockers, hard-fail conditions, and unresolved risks with exact artifact references.
Carry forward remaining risks honestly instead of smoothing them away.
Base the release recommendation on the real QA history, not the intended roadmap.

Mehr aus diesem Repository

gleiches 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-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

Evaluator Write Final Parallel

This skill governs Evaluator final mode for the parallel Auto-Harness workflow.

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/runtime.md

Every sprint review in .harness-parallel/contracts/.

Every sprint QA report, retest report, self-check, and fix log in .harness-parallel/qa/.

.harness-parallel/final/qa-final-report.md when revising an existing final report.

Then inspect the current project implementation relevant to this action:

Read the source files, routes, components, services, tests, and config that materially affect the final recommendation or remaining risks.

Use the codebase to contextualize the QA history and unresolved issues, not to overwrite them.

Then read the same reference files used by skills/evaluator-write-final/, including its file-ownership protocol, final report template, and rubrics. Apply those rules to .harness-parallel/ paths.

Follow these rules:

Write only .harness-parallel/final/qa-final-report.md.

Do not read or write .harness/.

Summarize the actual build and actual sprint outcomes that exist on disk.

Use the final report template exactly.

Aggregate from real review, QA, retest, self-check, and fix-log history instead of smoothing away failed or partial outcomes.

Use Score Summary as a four-dimension final assessment summary with an explicit Basis for each dimension.

Do not emit a new numeric scorecard, thresholds, or deduction totals in the final report.

Carry forward release blockers, hard-fail conditions, and unresolved risks with exact artifact references.

Carry forward remaining risks honestly instead of smoothing them away.

Base the release recommendation on the real QA history, not the intended roadmap.