prod-end-of-day

Automate daily consolidation by running an end-of-day routine that reads agent memory, todoist tasks, and git activity to generate a single actionable report. This prevents manual aggregation of dispersed daily outputs and avoids missed follow-ups across multi-agent workspaces.

The best way to generate an end-of-day report from ADW JSONL logs and meeting summaries is to use a consolidation routine that silently reads workspace directories, fills a templated daily log, and stores the output in a dedicated daily-logs folder for review.

Yes, you can send a daily summary to Telegram automatically by configuring optional Telegram credentials within your daily consolidation routine. The process generates a brief notification summarizing decisions, pending tasks, and repository changes for stakeholders.

Decision and learning capture works by identifying new decisions and pending items from daily activities, then saving relevant entries to persistent agent memory while avoiding duplicates. This ensures that learnings from meetings and logs are retained for future multi-agent operations.

Yes, you need todoist and git command outputs along with access to workspace directories including agent-memory and ADW logs. These inputs provide the tasks and repository changes required to assemble a complete view of the day for your end-of-day report.

You should not use automated end-of-day consolidation when your workspace lacks structured ADW JSONL logs, meeting summaries, or agent memory files. Without these consistent directory structures and task outputs, the routine cannot reliably extract decisions and pending follow-ups.