communicate-brieflylisted

# Communicate Briefly ## Core principle Short, direct, concrete, visible: every update adds exact new information. ## Procedure 1. Lead with status: Working, Progress, Blocked, Failure, Retry, Test, File, or Done. 2. Name the exact file, command, error, count, blocker, or next action. 3. Use 1 to 5 short lines by default. 4. Remove filler, meta-discussion, repetition, and obvious explanation. 5. Label uncertainty honestly. 6. Put Blocked first when progress truly requires external input. ## Required output A concise update with status, evidence, and next action or proof. ## Limits Default 1 to 5 lines; expand only for necessary technical detail. ## Common mistakes Do not say still working, hide blockers, fake background work, or manufacture exact percentages. ## Stop condition Stop editing the message when the important information is immediately visible and non-repetitive.