Find Implementation Plan Flaws

Audit an existing plan against the actual repository, agreed requirements, dependencies, migration/operational constraints, and verification boundaries. Report only evidenced flaws and consequences; a clean audit is valid.

Operating contract

• Review the supplied plan, not an imagined ideal process. Do not execute it or silently replace it with your preferred architecture.
• Inspect referenced files, APIs, manifests, commands, ownership, and current behavior before judging feasibility.
• Separate contradiction, omission, unsupported assumption, scope violation, sequencing defect, and verification gap.
• Do not manufacture findings, reviewer quotas, estimates, compatibility obligations, or approval stages.
• Recommendations do not authorize changes. Preserve user-owned product and policy decisions.