An agent that writes our Monday status report

The Monday progress report takes an hour of gathering: rereading the tasks, finding what was said in meetings, checking what has really gone out. When it is condensed in a hurry, carried-over actions disappear without anyone having done them, and you rediscover them when a client follows up.

On Monday, it writes the report of the week that has just ended. It reads the mandates in Twenty, the closed, open or merged tasks in GitLab, the meetings filed in the Drive and the week's emails. It starts from the previous report, counts the actions still open, then writes a file in the same template every week, filed in the same place of the team Drive.

For a client, it prepares the weekly report the same way: written for the client, updated just before the meeting, completed afterwards with the transcript.

Four rules, written down rather than left to intuition:

• Emails correct meetings. Meetings announce what is to go out, emails say what has gone out. A draft is not a sent message: only a sent one proves it.
• An action not done stays visible. Every open action of the previous report is either carried over or removed because a source shows it done. Condensing erases nothing.
• The Drive file is the reference. A shared document is a generated output, never a second version kept by hand.
• Written for its reader. A client report contains no internal note, no secret, no unapproved amount.

A report in short form, for an imagined week (illustrative example, fictional content):

• Done. The login module is delivered: the fix is merged and in production.
• Decided. The switchover is pushed back a week, to leave time for acceptance testing.
• Carried over. Send the client their access. The meeting announced it, no email went out: the action stays open, marked as carried over.
• To decide. Keep or drop the option in testing, before the next report.

• Carrying over is more honest than condensing. A carried-over action is seen and discussed; a vanished one is rediscovered at the worst moment.
• Crossing two sources beats trusting one. Without the emails, a report once asked for an access that had in fact gone out several days earlier.
• A constant template reads faster than its content. You know where to look, from one week to the next.

The same pattern works for any recurring report: steering committee, sales review, a site's activity report, construction follow-up. A fixed template, cross-checked sources, a visible carry-over of actions not done, and a person who reads it before the meeting.