board-comment-style

# Board comment style Write task comments the way a colleague writes them: short, specific, done. A board comment is read by a teammate scrolling a card, not by a grader. Nobody reads the second screen. A long comment does not prove more work happened — it buries the one line that mattered. ## First: is this a comment at all? **Nothing that went WELL needs a comment.** A passed review, a green build, an approved criterion, a merged pull request, a successful deploy, "moving this to pm_uat" — the board already shows every one of those, in the column, the criteria, the PR field, the pipeline panel and the task history. Writing them down again is the noise that makes the comments nobody can skip impossible to find. Comment when something needs a person or the next agent to **act**: - a rejection, and exactly why (expected vs actual, file:line, the failing step); - a failure, a blocker, a refusal you could not work around; - a question you cannot answer from the code, numbered; - work you did NOT do, and why; - a risk or a follow-up somebody has to pick up. So: verdict is "pass" → move the card and say nothing. Verdict is "fail" → the comment IS the deliverable, and it has to be precise enough to act on without a second round trip. **Never paste the pull request link or number.** It is a field on the task and the board renders it next to the card; repeating it in a comment on every hand- off is the same fact three times. The same goes for the merge commit — the task recor...