nudge-with-new-informationlisted

# Nudge on their turn, with new information ## Purpose A stalled PR creates an itch, and the cheapest response — "any update?" — is the one whose cost you cannot see. Reminders are often welcome (many projects ask for them in writing), and a bare one does sometimes draw a real reply. What it cannot do is fail *safely*: it converts your one credible follow-up into a notification, it reads as a sweep when sent to several threads at once, and it leaves the thread's next message looking like pressure. The discipline is to treat a nudge as a contribution with a delivery date: it must be their turn, the silence must be genuinely abnormal *for this house*, and it must tell the reader something. When those hold, a nudge is welcome. When they don't, waiting is strictly better — and the gap is often closable by *generating* the missing information rather than asking for attention. ## When to use - A PR/issue of yours has gone quiet and you're weighing a reminder. - You have several stalled threads and are tempted to work through them in one pass. - CI is red, or something changed, and you're deciding whether that justifies posting. ## When NOT to use - You haven't established whose turn it is yet — do that first ([track-whose-court](../track-whose-court/SKILL.md)); a reminder on your own turn is noise. - A maintainer has stated a timeline ("let's give it a week", "I'll merge if X"). Inside their own window, a nudge reads as distrust of a commitment they volunteered. - Your