quick-recap

Append a single-line status signal to the end of every completed response so work-state is unambiguous at a glance — green (done), yellow (done but a specific non-routine step remains), or red (blocked on the user). Use this on any task that produces a deliverable, edits files, ships code, or completes a step in a longer loop. Especially important for unattended or parallel agent loops where the operator needs to scan many outputs and instantly tell which finished clean, which need one manual step, and which are stalled. Trigger on completion of any substantive unit of work; also when the user says "recap", "status", "where are we", "what's the state", or wires this into a scheduled or multi-wave run. Do NOT emit a status line for pure conversation, questions, or clarification turns — only for work with a definite end-state.