shape

Problem scoping alignment requires a falsifiable problem restatement and iteration until a shared understanding exists. You must define scope boundaries, success criteria, and out-of-scope constraints to prevent engineering from misreading the target problem.

A falsifiable problem restatement reframes the target problem in PM vocabulary so its boundaries can be tested and validated. You need this when a PM has a target problem requiring confirmation of scope and out-of-scope constraints before any design decisions.

Requirements validation involves surfacing the single load-bearing PM-altitude uncertainty with the highest probability-weighted rework consequence. This forces articulation of the most critical scope boundary rather than tactical doubts to prevent invalidating the plan later.

Yes, this approach supports a structured handoff by producing a frozen, PM-ratified problem-set artifact. This artifact acts as a decision gate that chains directly into plan preparation without requiring any other skill invocation.

Skipping PM-EM alignment causes the EM to begin solutioning from a misread, leading to architectural rework. Without a ratified problem-set exit gate, planning proceeds on tactical doubts rather than a confirmed, falsifiable problem scope.