engineering-fix-orchestrator

Cross-layer orchestration applies safe sequencing to multi-layer engineering changes across backend, frontend, contracts, migrations, and worker pipelines, routing steps from evidence to verified handoffs.

Sequencing incident-response fixes requires separating root-cause from symptoms, routing steps to focused skills, and enforcing per-layer verification gates before completing the handoff.

You need cross-domain orchestration when an incident or feature request requires multi-domain coordination, staged edits across distinct layers, and a final end-to-end proof gate before release.

Create a verification plan by defining per-layer checks and an end-to-end proof gate, identifying blockers and dependencies before routing the final handoff for implementation.

No, this workflow is explicitly not for PM or product roadmap planning, but strictly coordinates multi-layer engineering changes requiring staged edits and verified handoffs.

Separating root-cause from symptoms ensures evidence-driven routing, preventing superficial fixes by enforcing per-layer verification gates before the end-to-end proof gate handoff.