morning-brief

To consolidate overnight Slack messages and Jira updates into a single priority list, this morning briefing workflow aggregates cross-source signals, applies timestamp-based delta filtering, and ranks items by urgency. It deduplicates entries across passes to output a unified action plan.

The best way to triage unanswered Slack requests and stale Jira issues is through cross-source attention planning. It identifies standing obligations from the last 48 hours, detects blocked or unblocked work, and ranks everything into a priority-ordered table for immediate action.

Yes, you can generate a morning briefing without write access because the workflow requires read-only operation. It performs per-integration preflight checks and uses parallel collection to safely gather data, optionally writing state locally to workflow-morning-brief.state.json.

Timestamp-based delta filtering works for daily team process reporting by comparing current Slack and Jira signals against your last run. It isolates new messages and updated issues since that timestamp, ensuring your morning brief only surfaces net-new activity requiring attention.

Yes, the morning brief workflow can update your focus configuration for pulse monitoring. After generating your priority table, it offers an optional daily focus update to narrow what gets monitored, writing the configuration changes when appropriate.

The main limitation of using a read-only morning brief is that it cannot modify underlying Slack or Jira issues directly. It strictly focuses on aggregation and reporting, meaning you must execute the prioritized actions and resolve blocked items manually in their source platforms.