sdlc-plan-change-escalation

Emit a BLOCKER: PLAN_CHANGE_REQUIRED status with concrete evidence like curl transcripts or provider documentation. This plan-defect escalation protocol routes unimplementable plans back to the coordinator for triage and updates.

A plan change required escalation is a protocol for routing materially wrong SDLC plan artifacts back to the planning system. It triggers when architecture contradictions, missing endpoints, or unavailable provider capabilities prevent implementation.

Trigger a plan escalation when the plan itself is unimplementable, such as missing endpoints or unsendable wire formats. Do not use it for binding mismatches, missing credentials, or code-quality issues, which belong in defect-incident remediation.

You need concrete evidence such as curl transcripts, runtime errors, or provider documentation and changelogs. This evidence-based triage approach verifies the architecture contradiction and confirms prohibited alternatives before escalating.

No, wire format divergence between stories is explicitly ruled out as an escalation path. Plan escalation is reserved for materially wrong artifacts where required external behavior is unavailable, preserving clean routing and accurate completion contracts.

Verify provider capabilities by gathering runtime errors and checking provider documentation or changelogs to confirm the required external behavior is unavailable. You must also verify prohibited alternatives before emitting the PLAN_CHANGE_REQUIRED status.