All agent skills

Leading Deeper with AI / 06

Daily Debrief

Turn scattered notes and messages into an action list that checks earlier commitments and links back to evidence.

Available calendar, meeting notes and messages feed a source-linked AI debrief with proposed follow-ups and visible uncertainty. A person reviews it and chooses what matters.[1] [2]ContextAI briefYour review
AI generation or assessmentHuman input or judgment

Example result

Tonight. Tomorrow. Tracking.

Fictional example / AI draft

Your daily debrief

Tonight (0)

Nothing in the supplied sources needs action tonight.

Tomorrow (1)

  • Review Morgan’s rollout checklist

    Suggested next step. The checklist was posted; your review is still a decision.

    Source: msg-44 · 8 April, 14:10; previous brief

Tracking (2)

Keep visible; this does not mean done.

  • Confirm the review date

    The date change is proposed, not confirmed.

    Source: note-12 · 8 April
  • Track Avery’s dependency check

    No new update; progress is unknown and no due date was stated.

    Source: Previous brief + msg-21 · 7 April; no new supporting record
AI proposes priorities. You choose what to act on.
Sources and coverage

8 April 2030, Europe/Berlin. Calendar, meeting notes, two message threads and the previous brief. No email or issue tracker access.

Fictional illustration only, with invented people and records; it is not evidence from Jasmine's work or a live debrief.

Read the example JSON ↗
Use Daily Debrief ↑
Give your agent this context

Fictional example. Replace it with your own records.

One day
8 April 2030 · Europe/Berlin. Calendar, note, two threads + previous brief; no email or tracker.
Earlier commitments
Morgan: post checklist before Wednesday. Avery: check dependencies, no due date. [Previous brief + msg-21, 7 April]
Today’s updates
14:10: checklist posted [msg-44]. Thursday review proposed, unconfirmed [note-12]. No new Avery update. [8 April]
How it works
  1. You: Choose the sources

    Give your agent one day of calendar, notes and messages, your timezone and the previous brief.

  2. AI: Draft the action list

    Compare commitments with new evidence. Propose Tonight, Tomorrow and Tracking items, each with a source.

  3. You: Choose what to act on

    Check the evidence and adjust priorities. A missing update means unknown progress, not overdue work.

Use this format across AI tools
  • Red: Tonight, with only supported needs before signing off
  • Yellow: Tomorrow, with proposed next actions
  • Green: Tracking, including open questions and unknown progress, not a completed-work status
  • Source references and coverage limits; no message or task changes without your instruction

Use the AI tool approved for your work with supplied material. Wording and layout will vary by model; look for the evidence, uncertainty and review decisions shown here. Connections and recurring runs depend on your setup.

Connect your sources (optional)
01

Start here

Bring your context.

What you’ll need

  • Reporting period, cutoff, timezone and the identity whose activity is being reviewed
  • Work focus: leader, individual contributor (IC) or mixed; use the sources relevant to that work
  • Approved calendar, notes, messages and email, or supplied excerpts
  • Optional document/comment changes, PR reviews, CI notifications and issue records
  • Previous private brief, commitment record and last successful coverage boundaries, if available
  • Preferred attention sections, such as Tonight, Tomorrow and Tracking
  • Authorized private output destination, or return a draft in the current response

MCP & tool setup

Start with approved excerpts. Connected use needs only the read tools for your selected focus: messages, email, documents/comments, calendar or delivery records.

Read calendar contextPossible toolsCalendar

Needed when: Only when the user wants live calendar context instead of supplying event records.

MCP or tool examples
An approved Google Calendar or Outlook Calendar connector or MCP · An approved calendar export
Tools must support
Read events and relevant changes within the reporting period; Retain timezones, cancellations and stable event references; Distinguish scheduled activity from evidence of attendance
Access needed
Read access to the specified calendars and period. Creating events, accepting invitations and modifying calendars are unnecessary.
Without that connection
Provide selected calendar entries or a redacted export with dates, timezone and status.
Read meeting notes and documentsPossible toolsDocs / DriveFiles

Needed when: Only when selected notes, document changes or comments are needed and are not supplied directly.

MCP or tool examples
An approved Google Drive connector or MCP with document reading · Another approved document connector · Approved local note exports
Tools must support
Find notes for the selected meetings in the agreed location; Read the relevant note content; Read selected document changes and comment threads when supported; preserve replies, timestamps and unresolved questions; Retain document references and dates; Check important AI generated claims against original statements where available
Access needed
Read access to selected notes or their approved folder. Do not request all Drive files, recording access or document editing merely to prepare a brief; recordings need their own authorization if required.
Without that connection
Provide approved note excerpts, changed text or comment threads with dates, source references and replies.
Read messages and commitmentsPossible toolsSlackTeams

Needed when: Only when the brief uses live Slack activity instead of approved message excerpts or exports.

MCP or tool examples
An approved Slack connector or MCP · An approved Microsoft Teams connector or MCP for an alternative chat source · Approved conversation exports
Tools must support
Retrieve the user's sent messages, relevant received messages and mentions within the agreed scope; Read the selected threads with surrounding context and replies; Retain message identifiers, links and timestamps; Report pagination, search and retention limits
Access needed
Read access to the named channels and explicitly approved conversations, including private conversations only when within scope. Verify actual search and thread reading tools; messaging and administration permissions are unnecessary.
Without that connection
Provide selected message threads with dates, sender context and source identifiers; state what is not covered.
Read optional email contextPossible toolsEmail

Needed when: Only when selected Gmail or Outlook conversations are relevant and explicitly included in the brief.

MCP or tool examples
An approved Gmail connector or MCP · An approved Outlook email connector or MCP · Approved email excerpts
Tools must support
Read the named threads or scoped reporting period; Include relevant replies and authorized attachments; Retain dates and message or thread references
Access needed
Read access to the selected mailbox scope. Sending, forwarding, deletion and mailbox administration are unnecessary.
Without that connection
Supply redacted email threads with dates and enough reply context to distinguish a request from a commitment.
Read optional delivery and issue evidencePossible toolsGitHubGitLabIssues

Needed when: Only when the brief checks commitments against GitHub, Linear or Jira activity that was not supplied directly.

MCP or tool examples
GitHub MCP or an approved repository connector · An approved Linear connector or MCP · An approved Jira connector or MCP · Approved work record exports
Tools must support
Read scoped issues, pull requests, reviews and relevant discussion; Read requested review state and relevant CI check/run results when supported; match the PR, commit and timestamp; Inspect current recorded state and dated changes; Retain stable references and distinguish recorded state from the broader outcome
Access needed
Read access to the agreed repositories and projects. Creating or editing issues, assigning people, merging and changing project state are unnecessary.
Without that connection
Provide dated PR/review excerpts, CI notifications or issue records with stable references. Label notification-only CI status as a report at its send time.
Read or save the debriefPossible toolsFilesDocs / Drive

Needed when: Read access is needed only to retrieve an existing prior brief; writing is needed only when the user has separately authorized a specific private output destination and continuity update.

MCP or tool examples
Approved local file tools · An approved private document or storage connector · A prior brief supplied in the prompt
Tools must support
Read the previous brief, commitments and source coverage boundaries; Preserve identifiers, first seen dates and evidence history; Save a new brief and advance fully covered source boundaries only when authorized and successful
Access needed
Limit access to the approved private location and retain only what the brief needs. Without write authorization, return the draft and proposed state changes in the current response; do not create storage, publish files or set up a schedule.
Without that connection
Paste the prior brief and commitment record, then copy the returned draft to a private location yourself.

No live connection? Supply approved calendar records, meeting notes, message excerpts and the previous brief with dates and source references. Return a draft and explicitly state the sources and periods that were unavailable.

Use the full prompt instead
02

Copy. Adapt. Try.

Make it your own.

01Gather context

Use approved calendar, notes and messages when available; add delivery or email evidence only if useful.

02AICheck commitments

Link each possible commitment to its source and flag what needs confirmation.

03AIDraft the brief

Separate supported facts, proposed follow-ups and uncertainty.

04HumanChoose what matters

You decide what to act on; sending messages or changing work needs a separate instruction.

Replace the bracketed inputs. Use context you’re authorized to share.

Download .txt

Copy the template or select the text directly.

Using an agent? Other formats

Adaptable public template based on the talk; not the original internal prompt.

Review checks
03

Keep your judgment in the loop

Review the result.

01

Can I verify each substantive statement and status change from its source?

02

Does the brief distinguish what happened, what remains unknown and what the agent proposes?

03

Did it preserve earlier commitments and make retrieval gaps visible without inventing progress or urgency?

04

Are the next priorities and responses still decisions for me?

What evidence should you look for?
  • Compare the draft with the approved source window and record missed or incorrect commitments and status changes.
  • Track preparation and human review effort separately from agent runtime, along with useful corrections and source coverage.
  • Test a repeated run and a missed day catch up to confirm that commitments are not duplicated and retrieval gaps remain visible.
  • Do not treat absent updates as incomplete work or claim time savings without a comparable baseline.
How this connects to the talk

An approach I brought to work

From practice to work.

Softball IQ

I built customer service and marketing debriefs for Softball IQ.

At work

I brought that approach into my day job to prepare a source linked daily debrief and check earlier commitments.

Your judgmentYou decide what matters, what needs a response and which commitments should change after checking the supporting evidence.

Value to checkCompare preparation and review time with your previous routine, and track missing commitments, incorrect summaries and useful follow through.