des-correct-course

Recover a derailed data engineering workflow by diagnosing the root cause of the derailment and generating a structured correct-course plan. This plan enumerates impacted artifacts, required updates, and rerun recommendations to safely route execution back to the appropriate DES phase.

Diagnose root causes for release blockers by identifying symptoms like missing upstream artifacts, wrong dependency ordering, or contract gaps. The process maps these issues to a structured symptom register and risk assessment to target the specific workflow failure point.

Fix missing evidence and dependency ordering problems by producing a targeted impact analysis and safe correction plan. This plan specifies required artifact updates and workflow status guidance without blindly continuing or rewriting upstream work.

No, this workflow correction process halts when fix requests attempt direct code changes or when evidence is insufficient. It focuses on planning artifact updates and recommending next skill reruns rather than executing code modifications.

Yes, artifact governance automation supports sprint planning recovery by identifying missing upstream artifacts and rerouting the workflow. It assesses the scope of implementation impact and generates rerun recommendations to safely restore release readiness.

Avoid using a correct-course plan when evidence is insufficient to diagnose the root cause, or when the goal is to directly rewrite upstream work. The process requires clear blocker-level inconsistencies or dependency ordering problems to generate valid routing guidance.