refine-plan

Plan refinement audits remaining work against completed phases to capture scope drift. Adversarial reviewer cycles surface stale references and missing specifications, iterating until convergence to produce a formal plan update.

Adversarial plan review dispatches devil's advocate reviewers to surface references, assumptions, and gaps in remaining work. It iterates until convergence, preserving the immutability of shipped work while generating a formal review trail for audits.

Phase-aware editing touches only the remaining phases of your project plan, while completed content remains immutable and verifiable via checksums. This ensures shipped work is preserved during the refinement cycle.

Yes, tracking drift between planned and actual execution generates a structured Drift Log and Plan Review trail. These convergence checks support robust project execution across multiple refinement rounds.

Auditing remaining work against completed phases dispatches adversarial reviewers to surface stale references and missing specifications. It produces a formal plan update cycle with in-place writes and a review trail for audits.

Automated plan refinement cycles target in-progress plans needing drift correction. If your project phases are fully complete or lack a formal plan file to audit, refinement cannot capture drift or iterate to convergence.