Video 7: customize daily briefing, shutdown routine, and weekly review workflows
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
c489dcf963
commit
2c0468f691
4 changed files with 175 additions and 128 deletions
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
name: daily-briefing
|
||||
description: Generate a morning briefing with your calendar, tasks, deadlines, and anything else you need to start the day.
|
||||
description: Morning briefing that pulls today's tasks from ~/notes/todo.md and gives a clear picture of what's on deck.
|
||||
triggers:
|
||||
- run my briefing
|
||||
- morning briefing
|
||||
|
|
@ -10,53 +10,40 @@ triggers:
|
|||
|
||||
# Daily Briefing
|
||||
|
||||
Produce a morning overview so you know what matters today.
|
||||
One command to start the day. Pull tasks, show what matters today.
|
||||
|
||||
## When to Use
|
||||
|
||||
Run this at the start of your day. One command, full daily picture.
|
||||
Run this at the start of your day.
|
||||
|
||||
## Instructions
|
||||
|
||||
1. Check today's calendar events (if calendar MCP is connected).
|
||||
2. Review any active projects or tasks in the workspace.
|
||||
3. Check for approaching deadlines (today, tomorrow, this week).
|
||||
4. Note any items that are past due.
|
||||
5. Produce a formatted briefing.
|
||||
1. Read `~/notes/todo.md`.
|
||||
2. Identify tasks marked for today or with no specific date (treat undated tasks as fair game for today).
|
||||
3. Identify any overdue tasks (past their date if dated).
|
||||
4. Produce the briefing below.
|
||||
|
||||
### Output Format
|
||||
|
||||
**Daily Briefing — [Date]**
|
||||
**Daily Briefing — [Weekday, Month Day]**
|
||||
|
||||
**Today's Schedule**
|
||||
[List of calendar events with times. If no calendar connected, note "Calendar not connected — add events manually or set up a calendar MCP connector."]
|
||||
**Today's Tasks**
|
||||
[Tasks from todo.md that are due today or are undated and in progress. Numbered list.]
|
||||
|
||||
**Active Projects**
|
||||
[List of current projects or tasks in progress, with brief status for each.]
|
||||
**Overdue**
|
||||
[Any tasks past their due date. Flag these clearly.]
|
||||
|
||||
**Deadlines**
|
||||
[Anything due today, tomorrow, or this week. Flag overdue items.]
|
||||
|
||||
**Notes**
|
||||
[Anything else worth knowing — reminders, follow-ups, items from yesterday that need attention.]
|
||||
|
||||
## Customization Ideas
|
||||
|
||||
This is a starter briefing. As you use it, consider adding:
|
||||
- Weather (requires a web search or weather API)
|
||||
- A motivational or reflective quote
|
||||
- Specific data from connected tools (email summary, Slack highlights, etc.)
|
||||
- Sections for specific roles or modes of work
|
||||
|
||||
The assembler in Video 7 will help you customize this to your actual needs.
|
||||
**Later This Week**
|
||||
[Tasks with future dates this week, so you know what's coming.]
|
||||
|
||||
## Rules
|
||||
|
||||
- Keep it scannable. Use short lines and clear sections.
|
||||
- Flag anything overdue or time-sensitive at the top of its section.
|
||||
- Don't editorialize. Present facts. Let the reader decide priorities.
|
||||
- If a data source isn't connected, say so rather than skipping the section silently.
|
||||
- Keep it scannable. Short lines, clear sections.
|
||||
- If todo.md doesn't exist yet, say so and offer to create it.
|
||||
- Don't editorialize. Present the tasks as written. Let Connor decide priorities.
|
||||
- Overdue items always appear, even if the list is long.
|
||||
- If there are no tasks in a section, omit that section header.
|
||||
|
||||
---
|
||||
|
||||
*Started with the Robot Assistant Field Guide Starter Kit. Customized in Video 7 via the assembler.*
|
||||
*Customized in Video 7 via the assembler.*
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue