sdlc-plan-change-escalation

What problem does it solve?

This Skill provides a precise protocol for escalating a materially wrong SDLC plan artifact that cannot be fixed through defect-incident remediation, preventing wasted iteration and silent plan drift.

Core Features & Use Cases

• Plan-defect escalation trigger: Emits a strict BLOCKER: PLAN_CHANGE_REQUIRED escape hatch when the plan itself is unimplementable (e.g., missing endpoints, unsendable wire_format, architectural contradictions, or unavailable provider capabilities).
• Routing-safe and evidence-driven: Requires concrete evidence (curl/transcripts, runtime errors, provider documentation/changelog) so the coordinator/planner can triage and update the plan.
• Protocol boundaries: Explicitly rules out incorrect escalation paths (binding mismatches, missing credentials, wire_format divergence between stories, incident scope expansion, code-quality issues) to preserve clean routing and accurate completion contracts.

Quick Start

Use sdlc-plan-change-escalation when your implementation verification shows the plan references an endpoint that does not exist or otherwise cannot be executed as written.