test-with-proof

name	test-with-proof
description	A test-focused procedure that writes a failing or contract-revealing check, makes it pass without unrelated behavior changes, and proves the new check is part of completion. Use this skill when the request mentions tasks that exist to add or repair verification, implementation follow-up work that still lacks behavior coverage, contract checks for harness surfaces.

Generated from Skill IR: test-with-proof@1 Do not edit this generated file directly unless this repository intentionally allows generated-surface edits. Update the Skill IR source instead.

Test With Proof

Use this when

Use this when triggers match: test, coverage, validation, proof, regression protection.

Job to be done: add or repair verification that catches the intended behavior and is included in the proof path.

What to do

1. Identify the behavior under test and the intended failure signal.
2. Write a failing or contract-revealing check that exercises the real behavior.
3. Run the check and confirm the expected signal.
4. Make the smallest change needed to make the check pass without unrelated behavior changes.
5. Run the proof path that includes the new check and read the output.

Evidence required

• behavior-under-test note
• failing or contract-revealing check
• red-green evidence when applicable
• proof output

Bundled resources

• .agent-harness/routes/test.json (reference): keep the testing procedure aligned with the route card that governs verification-only work Use when the task is primarily about tests or validation.
• docs/specs/verification-system.md (reference): tie the new check to the repository proof model and completion rule Use when the operator needs to confirm that the verification surface supports the final claim.

Evaluation prompts

• contract-check: Add a harness contract check for a missing behavior and prove it fails before the implementation change. Check for: captures a real failure signal; keeps the change scoped to verification when possible; proves the new check is part of the final proof path.

Forbidden behavior

• tests that only validate mocks instead of real behavior
• tests that pass before they can fail
• folding unrelated production changes into the testing slice
• claiming the check works without rerunning proof

Done when

• the new check catches the intended behavior
• the proof path includes the new check
• the testing slice does not smuggle in unrelated changes

This generated Claude-style skill follows the 9arm-skills shape: one skill directory, one SKILL.md, YAML frontmatter, and behavior-preserving body generated from Skill IR.