Purpose
Assess pipeline structure and coupling risks to reduce fragile orchestration and hidden dependency failures.
When to Use
- Reviewing ETL/ELT architecture changes.
- Auditing dependency edges across jobs/services.
- Planning safe refactors in data processing flows.
When Not to Use
- UI-only tasks unrelated to data flow.
- Single-file changes with no upstream/downstream impact.
- Pipeline modules and orchestration entry points.
- Dependency definitions and schedules.
- Failure/retry semantics.
Step-by-Step Workflow
- Map upstream/downstream dependencies.
- Identify tight coupling and non-obvious ordering constraints.