proofline
TR

verify-proof

Purpose

Mechanical proof that a frozen plan was implemented: every acceptance criterion has a successful test or recorded command evidence, changed paths stay inside scope, and build, test and lint commands pass.

Source Skill purpose

When to use it

Use verify-proof after implementation to prove mechanically that the frozen plan is represented by code, tests and commands. Each acceptance criterion needs an exercising assertion or permitted recorded command evidence. Build, test and lint run sequentially, changed paths are checked against scope, and dependencies and contracts are compared with the plan. A failure already present at the base revision is marked pre-existing rather than blamed on the change. Design documents receive a synchronization check when applicable. The report ends with a validator-computed verdict, not a reviewer guess.

Source Skill purpose

How it works

Steps of the skill, in source orderEach numbered step follows the skill definition and links to its source.1. Read frozen inputsFlow2. Discover commandsFlow3. Run sequential checksFlow4. Check base failuresFlow5. Map criterion coverageFlow6. Check scopeFlow7. Check contractsFlow8. Sync design documentsFlow9. Write verificationFlow10. Validate verdictFlow11. Clean the baselineFlow
Steps of the skill, in source order

Source Flow

  1. Read frozen inputs Read criteria, scope, mapped tests and expected commands from the task and plan.

    Source Flow

  2. Discover commands Find build, test and lint commands and their sources, then record local and CI runtime versions using runtime-versions.sh.

    Source Flow

  3. Run sequential checks Run build, lint and test one at a time on the unchanged working tree.

    Source Flow

  4. Check base failures Repeat each unsuccessful command at the base revision to identify pre-existing behavior.

    Source Flow

  5. Map criterion coverage Link each acceptance criterion to a successful, asserting test or eligible command evidence.

    Source Flow

  6. Check scope Run mechanical scope and freeze checks against the task-owned paths.

    Source Flow

  7. Check contracts Compare dependency and contract changes with their frozen plan sections.

    Source Flow

  8. Sync design documents Run the design-document check when the configured documents and task class require it.

    Source Flow

  9. Write verification Record commands, criterion coverage, scope, design sync and pre-existing failures.

    Source Flow

  10. Validate verdict Run the verification validator against the task and frozen plan.

    Source Flow

  11. Clean the baseline Remove the recorded base worktree after the comparison is complete.

    Source Flow

Key rules

  • Back every verification row with command output or a checked source location.

    Source Hard rules

  • Let the validator compute the verdict from report rows.

    Source Hard rules

  • Count a criterion only when a real assertion or permitted command proves it.

    Source Hard rules

  • Use the scope checker rather than judging changed paths by eye.

    Source Hard rules

  • Do not edit product code or tests to obtain a successful verification.

    Source Hard rules

Output and gate

Output

  • Write the verification report with command results, coverage and a computed final verdict.

    Source Output

  • For standalone work, report the verdict and the row that prevents completion.

    Source Output

Gate

The skill definition states no gate rule.

Source Skill definition

Source

Source Skill definition

← All skills