using-des-skill

To prevent skipping upstream artifacts in data engineering workflows, use phase dependency detection to scan planning outputs and halt routing when prerequisites are missing. This enforces disciplined coordination by finding the earliest missing artifact before proceeding.

Checklist gate enforcement for data engineering project status updates requires loading a checklist file and evaluating Pass, Needs Work, or Blocked status before allowing completion updates for artifact-producing skills. This quality gating prevents premature status marking on unverified deliverables.

To route data engineering work through the correct project phase, select an adaptive workflow mode like Quick Fix, Standard Feature, Enterprise Data Product, or Correct Course based on risk and upstream artifact availability. The routing mechanism then selects the appropriate next phase skill automatically.

Yes, persona management coordinates cross-persona transitions in data engineering projects by selecting a primary persona from docs/personas.md or fallback mapping. It states what the persona owns and manages transitions without weakening quality gates or checklist enforcement.

Yes, workflow routing supports auditing and resuming existing data engineering projects by scanning resolved DES planning outputs to detect missing artifacts. It applies to starting, resuming, auditing, and coordinating projects across all four routing modes.

You should not override missing prerequisites in phase dependency detection unless explicitly required, because halting on missing dependencies prevents downstream quality issues. Overriding bypasses upstream planning artifact checks and risks unverified deliverables entering the workflow.