mine.implementation-review

Post-implementation code review compares changed files against design specifications using an automated checklist to verify design adherence. It applies a 7-category quality gate to identify implementation gaps and provide an actionable verdict before merging.

A quality gate for completed features audits implemented code against work packages to prevent technical debt. It systematically checks for common implementation pitfalls across 7 categories and outputs an approve, fix, or abandon verdict to ensure integration points are solid.

Checking design adherence involves diffing changed files against the original design document using an AI subagent. This automated checklist review confirms that all requirements are met and code is clean, providing clear feedback on whether to approve, fix, or abandon the implementation.

Yes, an automated implementation review requires git for diffing changed files and a temporary directory for review output. These prerequisites allow the AI subagent to systematically compare the implemented code against the design document and work packages.

The implementation gap analysis verdict provides a clear approve, fix, or abandon decision based on a 7-category checklist. It ensures design adherence and delivers actionable feedback to resolve any identified implementation gaps or integration issues.