10x-impl-review

Automating implementation review requires comparing actual code against a plan file to detect drift, dangerous decisions, and pattern non-compliance. You provide the plan path, and the review generates a findings report with severity, impact, and recommendations.

Implementation drift detection identifies dangerous decisions and pattern non-compliance by comparing actual code against original implementation plans. It ensures code quality and safety by flagging deviations during the review process.

Reviewing a specific phase for safety and pattern compliance involves running a phase review against your implementation plan. This quickly isolates dangerous decisions and drift for that stage, generating targeted findings.

Yes, an implementation plan file is required to check code for pattern compliance. The review process compares actual code repositories against these plans to identify drift and ensure safety standards are met.

Generating a findings report with severity levels requires performing a full plan review comparing code against implementation plans. The resulting report details severity, impact, and recommendations for any detected drift or non-compliance.

Yes, you can resume a saved implementation review session using the resume triage feature. This allows you to continue checking code for drift and pattern compliance without restarting the full analysis.