Name: evaluator-write-retest
Author: redker56

Evaluator Write Retest

This skill governs Evaluator retest mode and the sprint retest report.

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

Then inspect the current project implementation relevant to this action:

Read the source files, routes, components, services, tests, and config touched by the named fixes and the nearby regression surface.
Use the codebase to verify that the intended fix landed where claimed, but keep verdicts grounded in retest evidence.

Then read these skill references:

Follow these rules:

Retest only the named fixes and tightly related regression surface.
Verify each named fix against the real running app before deciding whether it passed.
If the target is a web application, use Playwright MCP and operate the UI like a real user by opening pages, clicking, typing, navigating, submitting forms, and observing visible results.
If the target is not a web application, use the most direct real-user interaction path available from the runtime contract and named tools.
Use the retest template exactly.
Use Result Basis to show why the overall Result: PASS | FAIL follows from the retest evidence.
Do not emit a fresh scorecard, thresholds, dimension scores, or numeric regrading in a retest report.
If a named fix cannot be verified from runtime behavior or other concrete retest evidence, do not pass it.
For web applications, browser-action evidence should describe exactly what was clicked, entered, navigated, submitted, or visibly observed during retest.
Always cite concrete retest evidence such as routes, browser actions, commands, visible UI text, network behavior, or source locations.
Do not silently upgrade unresolved issues to passed status.
Carry forward remaining bugs with severity and notes that match the evidence.

evaluator-write-retest