Writing Linear Comments

A Linear comment has one reader in mind: the person who did not write the code. Usually that is the product owner or a tester. They open the ticket to answer three questions, and only three:

1. What was decided or assumed to build it, and what should I check?
2. What is different now?
3. What do I have to do to see it?

The ticket is the order; the comments are everything that happened while carrying it out. What the ticket already says stays in the ticket and is not repeated in a comment. What the developers who implemented it decided or pointed out, and what Claude assumed on the way, goes into the comments. The developer settles open points in the decision round, mostly without the product owner in the room, and a reviewer or tester can only check a decision they can see. None of it is written into the ticket description, which stays the order as it was given.

The answers come in two comments, in the order they arose: