Weekly summary assistant

[slobentanzer]

Setting: in a chat, Friday, noon.

The user gets a message from the bot, initiated by a timed action. The bot is a dedicated instance containing a system prompt that instructs it to help and remind the user in being brief, comprehensive, and informative. The instruction can include areas of work, such as scientific, technical, issues and bottlenecks, etc.

Bot: Is now a good time to draft your summary of the week on project X?

User: yes

Bot: Great, let's have a chat about the work you did. What did you mainly work on?

User: ...

## conversation about work, current issues and potential bottlenecks, administrative questions, etc.

Bot: OK, here is a brief summary that contains all relevant information: [...] Is this OK to post?

User: I would say that ...

Bot: OK, here's the updated summary; OK to post?

User: yes

Bot: Great, I have posted the summary to the project card.

Main functions:

• alignment of users on regular updates, help with being comprehensive but brief
• providing vetted summaries for project leads and PIs
• Allow manual override

Manual override case (e.g., the summary is trivial):

Bot: Is now a good time to draft your summary of the week on project X?

User: in fact, I have already done it, since it is not too long. Please post this: 
      "I got responses from all coauthors and have resubmitted the paper yesterday."

Bot: Great, I have posted the summary to the project card.

If the project was not subject to work, the bot can also move a card (or put a label, depending on the system):

Bot: Is now a good time to draft your summary of the week on project X?

User: I did not work on X this week, data from collaborators are still missing.

Bot: OK, should I put it on hold with the message that you are waiting for data from collaborators?

User: yes

Bot: Great, I updated the card and put it on hold.