task-status-updatelisted

# Task Status Update Record finished or moved work on a task so the reader can scan it in ten seconds. A good update answers five questions and nothing more: **what got done, what's left, what's blocked, what was decided, and what decision is now needed.** Everything else belongs in a linked doc. The failure mode this skill exists to prevent is the "slop grenade" — a 500-word essay dumped into a comment box with headers, self-corrections, and buried decisions, written as if the reader were another agent parsing a transcript. The reader is a human with forty tabs open. Write for them. This skill is target-agnostic. The *writing* is the same everywhere; only the *posting mechanics* differ. Identify the target (Jira, Notion, GitHub, Linear, or a plain post), draft the update the same way, and post it using the right tool. Target-specific detail lives in `references/targets.md`. ## The core contrast Two updates on the same work. Both are "accurate." Only one is usable. **Usable** (the whole update): > Blocked by INC0489468 **Not usable:** a ~600-word comment with five `##` headers, a file table, two callouts, a corrected cost estimate, and the actual decision ("narrow the scope and close") sitting in paragraph nine. The information is real. The reader will not read it, and cannot answer "is this done?" from a glance. Aim for the first. When the work genuinely needs more than a few lines, use a template (see `references/templates.md`) — never a freeform essay — and move th