npx claudepluginhub osovv/grace-marketplace --plugin graceThis skill uses the workspace's default tool permissions.
Design verification that autonomous agents can trust: deterministic where possible, observable and traceable where equality checks alone are not enough.
Verifies task completion by enforcing fresh automated test runs, runtime evidence review, and spec re-read in /dev workflow Phase 7.
Runs parallel specialized agents to verify implementations, run tests (unit/e2e/integration/perf/LLM), grade quality (0-10 scale), and suggest improvements. Use before merging.
Validates agent deliverables in multi-agent workflows with expected outcome specs, evidence trails, external anchors, fidelity checks, and failure reporting. Use for handoffs, audits, summaries, and external outputs.
Share bugs, ideas, or general feedback.
Design verification that autonomous agents can trust: deterministic where possible, observable and traceable where equality checks alone are not enough.
docs/development-plan.xml must exist with planned modules or module contractsdocs/verification-plan.xml should exist; if it does not, create it from the GRACE init template before proceedingdocs/operational-packets.xml exists, use its FailurePacket shape for failure handoff outputMODULE_CONTRACT, function contracts, semantic blocks, and existing tests first$grace-plan before building verificationVerification in GRACE is not just "did the final value match?"
It must answer:
Use contracts for expected behavior, semantic blocks for traceability, and tests/logs for evidence.
docs/verification-plan.xml is the canonical place where this evidence model lives.
Read the smallest complete set of artifacts needed for the scope:
docs/requirements.xmldocs/technology.xmldocs/development-plan.xmldocs/verification-plan.xmlWhen operating on one module, prefer that module's plan entry, verification entry, and local tests over rereading the whole repository.
If the optional grace CLI is available, grace module show M-XXX --path <project-root> --with verification is a fast way to read the shared/public module and verification context, and grace file show <path> --path <project-root> --contracts --blocks is a fast way to inspect the local/private contracts and semantic blocks that need evidence.
Read the module contracts, function contracts, and linked flows. Extract:
Turn these into a verification matrix before writing or revising tests. Keep the matrix synced into docs/verification-plan.xml.
For each critical path, define the minimum telemetry needed to debug and verify it.
At a minimum:
[ModuleName][functionName][BLOCK_NAME]Prefer stable structured logs or stable key fields over prose-heavy log lines.
docs/verification-plan.xmlUpdate the verification artifact so it becomes execution-ready.
For each relevant module, define or refresh:
V-M-xxx verification entryAlso refresh project-wide policy when needed:
For each scenario, decide which evidence type to use:
If an exact assert works, use it. Do not replace strong deterministic checks with fuzzy evaluation.
Write tests and harnesses that:
Typical trace checks:
Substantial test files may also use MODULE_CONTRACT, MODULE_MAP, semantic blocks, and CHANGE_SUMMARY if that makes them easier for future agents to navigate.
When strict equality is too weak or too brittle, use bounded semantic checks.
Allowed pattern:
Disallowed pattern:
Match the verification depth to the execution stage.
Do not require full-repository verification after every clean module if the wave and phase gates already cover that risk.
Make these levels explicit in docs/verification-plan.xml so execution packets can reuse them.
When verification fails, produce a concise failure packet:
Use this packet to drive $grace-fix or to hand off the issue to another agent without losing context.
If docs/operational-packets.xml exists, align the handoff to its canonical FailurePacket fields.
docs/verification-plan.xml synchronized with real test files and commandsWhen using this skill, produce:
docs/verification-plan.xml$grace-execute or $grace-multiagent-execute run