proof-of-work
Installation
SKILL.md
Proof Of Work
Prove changed behavior through the running application and produce an artifact
that demonstrates the result. If the repo provides /repo-proof, load it for
the project-specific protocol.
Unit tests, linters, and compile checks are required checks, not proof, unless they exercise the whole application behavior being claimed.
For docs, policy, scripts, or tooling, use focused checks instead of full-stack application proof unless the change affects runtime behavior.
Proof Claims
In a task or issue, describe the observable claims the implementation must demonstrate. Do not provide a checklist of commands or list routine checks such as unit tests and compilation.