Menü
Explicit-only. Verify completed work against its authoritative contract and report coverage, working-code evidence, material gaps, and the completion verdict.
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.
Basierend auf der SOC-Berufsklassifikation
Explicit-only. Run a named autonomous mode, repeatedly selecting, implementing, and shipping coherent work while preserving anything blocked.
Use globally installed `playwright-cli` for browser automation, UI inspection, screenshots, Playwright test debugging, or test generation. Trigger when a task needs browser interaction or test repair. Do not use for generic tests, web search, non-browser docs, or API-only work.
Explicit-only. Align a feature specification, produce a reviewed plan, complete the local work, and ship the pull request.
Explicit-only. Review a plan/task/context artifact set and report material findings.
Explicit-only. Ship one pull request, observe hosted CI and review feedback, follow PR policy, reply to every eligible comment, and request merge authorization before merging and cleaning up.
Use Agent Dispatch MCP tools only when the user names an external dispatch target or another skill explicitly requires dispatch. Do not use it for generic subagent, second-agent, or fresh-context requests; use the built-in subagent instead.
| name | verify-work |
| description | Explicit-only. Verify completed work against its authoritative contract and report coverage, working-code evidence, material gaps, and the completion verdict. |
Verify the final tree against its contract without fixes.
Require exact plan/task/context, or an explicit request and scope. Never
discover contracts from .agent-layer/tmp/.
Write .agent-layer/tmp/verify-work.<run-id>.report.md, using
YYYYMMDD-HHMMSS-<short-rand> for run-id.
references/contract-verification-rubric.md
to the current tree and touched files with evidence proportional to behavior
and risk.Read the contract/context, relevant diff, and final touched files. Use implementation reports only to locate deviations, skipped work, or evidence.
Record each contract item as complete, partial, missing, or unverified.
Assess supplements separately and identify material scope drift or undocumented
deviations without general code review.
Read COMMANDS.md, then run the narrowest credible checks; broaden only for
the contract. If any cannot run, report incomplete.
Direct inspection may be evidence when command output is not the right proof, but absence of evidence is not completion evidence.
Write a concise report containing the contract coverage and evidence, material findings, and exactly one final verdict:
completecomplete-with-follow-up: the contract is complete and remaining work is
explicitly outside itincompleteEach finding includes its contract item or location, current status from the rubric, evidence, and severity. Return the report path and verdict.