Use Task Completion Enforcer Prover with your AI.

Validate task completion

This capability exists because you. the LLM. forget requirements, leave placeholders, drift from scope, and declare done prematurely. This capability forces you to PROVE completion. WORKFLOW: (1) REQUIREMENT EXTRACTION. re-read the ORIGINAL user request word by word. Extract EVERY requirement as a numbered checklist. Not summaries. exact, specific, actionable items. If you cannot recite all requirements, you have forgotten the task. (2) COMPLETION EVIDENCE. for EACH numbered requirement, show the SPECIFIC artifact: file path, line number, function name, test result. "I did it" is NOT evidence. (3) GAP IDENTIFICATION. go through the checklist. Which requirements lack evidence? Which have placeholders? Which drift from the original request? Be BRUTALLY honest. (4) CONTINUATION. for EACH gap, DO THE REMAINING WORK NOW. Not later. Then call this capability AGAIN to verify the gaps are closed. (5) FINAL VERIFICATION. re-read the ORIGINAL request one last time. Compare EVERY line to your output. Does every requirement have evidence? If ANY axis fails: DO NOT declare done. Fix the gap. Call again. If ALL axes pass: DELIVERY_PROVEN. THE MOST BRUTAL PROVER. Forces the LLM to PROVE it finished what was asked. not claim completion, not summarize progress, but demonstrate with verifiable artifacts that every single requirement from the original request has been fulfilled. This capability exists because LLMs systematically declare "done" prematurely. Catches Requirement Amnesia (forgetting what was asked. a construction foreman is asked: "paint all 14 floors, replace carpet in lobby, fix elevator B, and install emergency lighting on stairwells." Foreman reports: "Building is done." Punch-list walkthrough reveals: floors 1-12 painted, floor 13 missed entirely, floor 14 half-done. Carpet replaced. Elevator B: "parts on order." Emergency lighting: "we did floors 1-5." The foreman forgot 3 of 4 requirements. He painted most of one requirement and called it done. Fix: extract the ORIGINAL request as a numbered checklist BEFORE starting work. Check each item off with physical evidence. not memory, not "I think I did it"), Premature Completion (declaring done without evidence. a kitchen health inspector has a 23-point checklist per station. Inspector walks through in 15 minutes, checks all 23 points as "pass" on the clipboard. Problem: station 4 (cold storage) thermometer reads 48°F. Requirement: ≤ 40°F. Station 7 (handwashing): no soap in dispenser. The inspector did not actually CHECK. they checked the BOXES. Completion without evidence is not completion. it is paperwork. For each checkbox: what specific observation confirms this passes?), Placeholder Infection (leaving TODO/FIXME/TBD in deliverables. an architect submits building plans: "Structural calculations: TBD pending soil analysis." "Fire escape route: see attached (no attachment)." "Electrical load: TODO." The plans are 85% complete. They are submitted as "final." The building department rejects them. 3-week delay. A placeholder is an admission that work is not done. If any TODO, FIXME, TBD, "coming soon," or "to be determined" exists: the task is not complete), Scope Drift (solving a different problem than what was asked. a farmer asks a veterinarian: "My cow is limping. Fix the limp." Veterinarian examines the cow thoroughly. Discovers a minor skin condition on the cow's back. Treats the skin condition. Writes a report about dermatological findings. Cow is still limping. The vet solved an interesting problem. just not the one that was asked. Fix: re-read the ORIGINAL request. Does your output address THAT request, not a related-but-different one?), and Verification Skip (never re-reading the original request before declaring done. an aircraft pre-flight checklist has 117 items. Pilot completes items 1-117. Signs the checklist. Ready for departure. But item 63 (fuel quantity) was checked against the PREVIOUS flight plan, not today's. Today's route is 400nm longer. Fuel is insufficient. The pilot checked every item but never re-read today's flight plan against the checklist. Verification is not checking your work. it is comparing your work to the ORIGINAL requirement. Rule: re-read the original request ONE MORE TIME after completing all work. Compare every line of the request to every line of your output). Call BEFORE declaring any task complete. If rejected, CONTINUE WORKING on gaps and call AGAIN