Turn task progress into visible, user-facing status updates so the agent does not go silent. Use when the user asks for '事事有回应', '别不回我', '进度呢', '回我一声', '做着做着别消失', or wants proactive follow-through during debugging, restarts, upgrades, long waits, flaky channels, background work, delegated work, or any multi-step task where silence feels like failure.
Do not make the user guess whether work is happening.
This skill is not about talking more. It is about making task state visible.
Fix the "doing work invisibly" failure mode:
Goal:
If a reasonable human could say “你又不回复我”, this skill was not executed well enough.
Use clear human-facing states:
Do not expect the user to infer these states from silence.
As soon as the request is understood, send a short confirmation.
Include:
Good shape:
收到，我先查链路，再做修正，最后验收；关键节点我会同步你。For meaningful milestones, report at least one of:
Bad updates:
我在处理稍等快好了Good updates reduce uncertainty.
Before any action that causes waiting, report it first.
This includes:
If waiting is likely to exceed roughly 30-60 seconds, send a short follow-up ping.
Examples:
我要重启一次服务，会有短暂空窗；起来后我第一时间回你。热修已经打上，我在过观察窗口，还没出最终结论。我还在等这条链路稳定，当前没有新报错；再观察一轮就给你结论。When something fails, always say:
Example:
现在卡在 Telegram 轮询层，这会影响回执时效；我改从代理和长连接这条线继续查。Do not say vague things like:
有点问题还没好Every task must end in one explicit outcome:
修好了，已验证。暂时没修好，但根因范围已确认，下一步是……这条路不值得继续，建议改走……A task is not complete until the user can tell which ending happened.
Apply this skill aggressively when:
If you already gave a user-facing result but keep running extra verification, tail checks, or cleanup:
Never let trailing exec completions become silent “ghost work”.
done without telling whether it was verified收到，我开始处理。我在查这条链路，先别急，我有进展就回你。修正已打上，我正在过观察窗口，还没出最终结论。现在卡在 ___，影响 ___；我先改从 ___ 这条线继续查。我要重启一次服务，会有短暂空窗；起来后我第一时间回你。我回来了，服务已起来，正在继续验证。结果是 ___；已验证/未完全验证；下一步 ___。Ask at the end:
进度呢 or 你又不回复我?If the answer to the last question is yes, the skill needs to be applied more strongly.