Prepare a Daily Brief

Create a practical view of what deserves attention today without forcing the user to reconstruct their day across calendars, messages, tasks, meetings, documents, and open work.

The goal is not a digest of everything that happened. The goal is a brief the user can act from.

1. Establish the purpose of the brief

Infer when possible:

• working day or time window;
• timezone;
• relevant workstreams;
• purpose;
• preferred format.

The brief may support:

• personal planning;
• executive orientation;
• a meeting-heavy day;
• operational exception management.

Ask only when ambiguity could materially change the priorities.

If an accepted daily-brief format already exists, reuse it. Otherwise start compact and let actual use determine the right sources, sections, and depth.

2. Gather context that can change today's plan

Use relevant approved context from:

• conversation;
• saved context;
• open tabs;
• files;
• calendar;
• email;
• team communication;
• project and task systems;
• meeting notes;
• documents;
• dashboards.

No single integration is mandatory.

Suggest connecting another source only when it materially improves coverage, accuracy, or speed.

Use the selected calendar as the default authority for scheduled commitments and the designated project, task, or communication system as the authority for its own records.

When records conflict, prefer current direct evidence and expose material contradictions rather than silently choosing one.

Respect privacy and scope boundaries. Do not include unrelated confidential work in a brief intended for wider sharing.

3. Determine what needs attention

Prioritize evidence likely to change what the user should do today:

• deadlines;
• meetings;
• decisions;
• commitments due or at risk;
• important unanswered messages;
• preparation needed for upcoming conversations;
• blockers;
• dependencies;
• missing ownership;
• meaningful changes;
• overdue work;
• newly urgent work;
• work waiting on the user;
• promised materials;
• conflicts between calendar, communication, tasks, and the apparent plan.

Use accepted priority rules when available.

Otherwise distinguish between observed urgency and your recommended priority.

Do not assume importance from message volume, sender seniority, or calendar presence alone.

Merge duplicate references to the same underlying work where possible.

Keep stale evidence, missing data, and unresolved conflicts visible when they affect the recommendation.

4. Produce an actionable brief

Default to a concise, scannable brief.

Use only sections that help that particular day.

Possible sections:

Focus

The few outcomes that matter most today.

Schedule

Meetings, deadlines, or timing constraints that change how the day should be planned.

Needs Attention

Messages, decisions, blockers, commitments, or actions requiring intervention.

Watch

Risks, dependencies, uncertain items, or developing situations worth monitoring.

Suggested Order

A practical sequence when priorities compete.

Include source links beside important claims where available.

Name owners and dates only when supported.

Keep facts separate from recommended priority when the distinction matters.

Avoid turning the visible brief into a full status dump.

5. Route deeper work when appropriate

Use the inbox-triage workflow when one communication queue needs detailed processing.

Use the open-loop workflow when commitments or ownership must be reconciled across multiple systems.

Use meeting preparation when an individual meeting requires deeper context than the daily brief should contain.

6. Prepare actions without silently executing them

The brief may suggest:

• reply;
• delegation;
• task update;
• calendar adjustment;
• escalation.

Prepare the smallest useful next action.

Keep these separately reviewable:

• sending;
• posting;
• rescheduling;
• changing ownership;
• updating external systems.

Before consequential execution, confirm the exact:

• people;
• account;
• destination;
• records;
• scope

unless already covered by active scoped permission.

After execution, report:

• completed actions;
• remaining blockers;
• unavailable sources.

7. Improve future briefs

After a real brief, learn what the user wants to:

• keep;
• remove;
• reprioritize;
• add.

Preserve durable preferences such as:

• trusted sources;
• priority rules;
• workstreams;
• depth;
• format;
• delivery destination.

Do not turn an unusual day into permanent policy.

When useful, preserve the accepted method as a reusable skill.

A recurring daily brief may be appropriate after the workflow is trusted and a real cadence exists.

It should define:

• workdays;
• timezone;
• selected sources;
• destination;
• review behavior;
• permitted recurring actions;
• stop conditions.

Do not automatically send messages, modify calendars, change assignments, or update records unless those exact recurring actions and destinations are explicitly approved.

Stop and ask when missing sources, account ambiguity, timezone uncertainty, privacy exposure, or conflicting evidence could materially change the recommendation.