Diagnose work that does not converge

Start only when the user names mo-convergence. A remark that work is slow, a long review loop or a failed attempt does not activate it, and no other skill calls it.

Read Feature lifecycle and Обратная связь о методологии completely: friction you hit goes to the user in your answer, and this skill writes no Issue.

Gather positions

Ask the agent doing the work, and every reviewer whose slot is still hot, one ordinary message each through the surface the lifecycle already uses: what is blocking convergence, what they themselves contributed to the delay, and what single change would unblock it. Do not start a new session to get an opinion, and do not wake a cold slot; a participant that is gone is recorded as unavailable, not reconstructed.