Loading

Daily bookends

A briefing to start the day and a wrap to close it.

10 minClaude Cowork
Loading

Set up

Try a plugin

The Productivity plugin ships with /start and /update as a starting point, already structured to read your calendar and channels and rank what matters. If your admin manages plugins and it's not available yet, skip this step. The prompt below works without it.

ProductivitySkills for inbox sweeps, daily rundowns, meeting prep, and decision logs
Add
/startRead calendar, inbox, and channels and write a one-page start-of-day briefing
Open in Claude
/updateLog what landed, what slipped, and queue tomorrow's opener
Open in Claude

Connect your tools

Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access.

Add a connector for each tool you want Claude to use.

Set your working folder

Create a Daily folder and point Claude at it. Each morning briefing and evening wrap writes there as YYYY-MM-DD.md, so the evening run reads what the morning run set out to do, and Monday's briefing can look back over last week. Create a project from that folder so your priorities, mute list, and tone stay attached.

Daily
2026-04-28.mdApr 28, 20263 KB
2026-04-27.mdApr 27, 20264 KB
priorities.mdApr 20, 20261 KB
In Cowork’s chat bar:Daily

The prompt

Copy this into Claude

Run my morning briefing. Tell me what's on fire, what's due, who's waiting on me, and the three things I should do first. Keep it under a page. Tonight I'll ask you to run /update and you'll write the wrap: what got done, what slipped, and what tomorrow opens with.

Daily

Why this works

Prompt

Name the sections you want. On fire, due, waiting on me, top three: a fixed shape you can scan in thirty seconds.

Prompt

Set a length limit. A briefing you'll actually read, not another inbox.

Prompt

Connect each run to the next. The wrap feeds tomorrow's briefing, so carry-over never drops.

Source

Let prior runs supply the context. Each run reads yesterday's file, so context compounds without you re-explaining.

Get a better draft

Practice

Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.

Practice

Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.

Make Claude work for you

A plugin skill is a starting point. Customize it with your own practices and expertise, or save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.

Make what we've done in this task so far into a skill, or edit the /start skill with my feedback.

Daily

Make it repeatable

Run it at 8am and 6pm

The briefing should be waiting when you sit down. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and the customized skills run on their own at the start and end of every workday.

Set up a scheduled task: run /start every weekday at 8:00am and /update every weekday at 6:00pm, both writing to Daily/<today>.md.

Daily
Scheduled taskActive
Daily bookends

Runs /start at 8am and /update at 6pm against Calendar, Slack, and Gmail and appends both to today's file in Daily.

Every weekday at 8:00am and 6:00pmOpen in Claude

Share with your teammates

Your customized /start and /update now carry your channel list, your priority rules, and your tone. Share them so anyone on your team starts and ends the day with the same one-page rhythm, and nobody's asking "what did I miss" in standup.

What changes for your day