task-validation

Task validation verifies that code actually exists, executes without errors, and passes tests before accepting completion. It enforces quality gates and acceptance criteria, catching paper solutions where documentation claims work is done but implementation is missing or broken.

Use automated validation to check file existence, run execution tests, and gather evidence like test results and integration proofs. This replaces superficial reviews with concrete verification that deliverables meet predefined standards and actually function.

Task validation automatically checks compliance with quality gates and acceptance criteria across claimed artifacts. It provides irrefutable proof through file paths, code output, and test results, preventing non-functional work from advancing to the next stage.

Yes. Task validation confirms new feature code exists, runs without errors, and passes unit tests. This prevents marking tasks complete until genuine implementation and functionality are proven, not just documented.

Documentation checks only verify that a task was described; task validation demands evidence. It executes code, runs tests, and verifies file artifacts to ensure real implementation exists and works, catching tasks that look done on paper but lack functioning deliverables.

Use it before marking tasks done, during code reviews, and at task handoffs. It's essential anywhere paper solutions pose risk—when incomplete or non-functional work could progress undetected and waste downstream effort or compromise product quality.