| name | tldr |
| description | Report a finished task as its result, not its transcript. Use when a task that produced an artifact or a run (a build, a workflow, a background agent, an implement or verify run, a release) has just finished and you are about to report it, and when the user types /tldr. |
A task just finished. Give its result, not its transcript.
Write in ASD-STE100 Simplified Technical English: one meaning per word, active voice, short sentences, no idioms. The length adapts to the task: a small task gets two or three lines, a large or noisy one gets more, never longer than the result needs. Choose the shape that reads fastest for this result: prose for a few outcomes, bullets or a table when several distinct items need scanning.
- Lead with the result: what the task produced or decided.
- Give the outcomes that matter, keeping exact paths, commands, names, and error strings, and linking commits, PRs, and files. Redact secrets: a token, key, password, or connection string that appears in a command or error is replaced with a placeholder, never reproduced.
- Close with what needs the user now, or "nothing" when the task is done.
Drop tool-call narration; keep outcomes. If the task produced nothing, say so; never invent progress.
Never explain what you were about to do, how you reasoned, or why the approach is sound unless asked. The user sees the diff and the output; do not restate them. No preamble, no sign-off. The summary is the whole reply. Stop.
