drift-analysis

To identify plan drift, you compare documented roadmaps and milestones against actual code changes. This drift analysis process cross-references evolving project data to detect misalignment, producing a prioritized reconstruction plan for course correction.

Documentation drift occurs when README, PLAN, or project docs no longer match implemented features. You detect this drift by analyzing documentation accuracy against the actual codebase, ensuring technical docs accurately reflect current software functionality.

You track issue drift and scope creep by cross-referencing stale issues and feature requests with actual implementation status. This scope drift analysis identifies feature creep and unresolved issues, generating actionable next steps for project realignment.

Yes, you can generate an executive summary of project drift by providing your docs, issues, milestones, and code changes. The analysis quantifies misalignment and produces a prioritized reconstruction strategy suitable for executive review.

You need to provide project data including documentation, issues, milestones, and code changes. Supplying these evolving project artifacts enables the detection of plan, documentation, issue, and scope drift to produce a reconstruction plan.

The best way to turn drift signals into a reconstruction plan is to analyze plan status, documentation accuracy, and feature completeness comprehensively. This transforms detected misalignment into actionable next steps and a practical recovery strategy.