The "Proof of Work" methodology prevents premature completion claims by requiring technical verification before stating that a task is finished. For example, instead of assuming an LSP configuration functions after a restart, we verify that the server starts and that tools respond to queries. This approach confirms the solution works before the user attempts validation.
Before claiming completion, provide reproducible evidence of the solution's performance and address edge cases. All claims must be backed by actual command output captured in the current environment.
NO IMPLEMENTATION WITHOUT A FAILING TEST FIRST NO COMPLETION CLAIM WITHOUT EVIDENCE FIRST NO CODE WITHOUT UNDERSTANDING FIRST
Enforces "prove before claim" discipline - validation, testing, and evidence requirements before declaring work complete. Use when claiming work is complete, recommending solutions, or finishing implementations, improvement validated, workflow optimized, performance improved, or issue resolved. Do not use when asking questions or for work clearly in-progress. MANDATORY: This skill is required before any completion claim. Source: athola/claude-night-market.