auditor

Verifying code implementation against a plan requires systematically comparing the codebase to plan requirements, running build and test checks, and generating a markdown audit report with step-level status and evidence to prevent incomplete changes from being accepted.

Detecting shortcuts during a code audit involves anti-shortcut detection to identify placeholders, deferred work, disabled tests, and fake implementations, ensuring superficially implemented changes are flagged before release readiness approval.

Evidence-based plan validation is confirming each plan requirement by locating relevant files, functions, and signatures, ensuring software delivery is complete by providing static evidence and dynamic test validation rather than relying on manual review.

You can use automated regression testing for release readiness audits by running builds and tests to validate implementation works in practice, providing dynamic quality checks that record whether the implementation meets plan requirements successfully.

The auditor does not modify implementation code during verification, requiring permission only to read project files, run test commands, and generate a structured markdown audit report with actionable recommendations.