connor/assistant-skills
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Video 7: customize daily briefing, shutdown routine, and weekly review workflows

Browse source 
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Connor Rhodes 2026-04-04 18:27:41 -05:00
parent c489dcf963
commit 2c0468f691
4 changed files with 175 additions and 128 deletions
Download patch file Download diff file Expand all files Collapse all files

13
_build-log.md
View file

@ -42,3 +42,16 @@
**Files updated:** AGENTS.md (Connected Tools section updated), skills/drafts-inbox removed, skills/_skill-index.md updated
---
## Video 7 — Building Workflows
**Date:** 2026-04-04
**Workflow type:** Weekly review (single session, typically Sunday, sometimes Saturday)
**Weekly review:** Reviews closing week against week note goals, two reflection questions, then plans new week and creates next week note at `~/notes/week_YYMMDD.md` (Monday date format)
**Daily briefing:** Pulls tasks from `~/notes/todo.md`, shows today's tasks, overdue items, and upcoming this week
**Shutdown routine:** Four steps: accomplishments review, victory lap (prompts voice journal), improvement reflection, plan tomorrow with one mandatory build/kaizen task
**Task store:** `~/notes/todo.md` (temporary; future: custom script to access task management program)
**Journal store:** Voice notes stored outside workspace (future: tool to access); assistant prompts the recording, does not save text
**Week notes:** `~/notes/week_YYMMDD.md` per week; template includes Goals, Notes, Reflection sections
**Files updated:** skills/daily-briefing/SKILL.md, skills/shutdown-routine/SKILL.md, skills/weekly-review/SKILL.md
---

53
daily-briefing/SKILL.md
View file

@ -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.*

107
shutdown-routine/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: shutdown-routine
description: End-of-day routine that reviews what happened, checks what's outstanding, and previews tomorrow.
description: End-of-day routine: review accomplishments, victory lap journal prompt, improvement reflection, and plan tomorrow's tasks including one build/kaizen item.
triggers:
- run my shutdown
- end of day
@ -10,52 +10,77 @@ triggers:
# Shutdown Routine
Close the loop on your day so your brain can stop working.
Close the loop. Review the day, capture wins, reflect on improvements, and set up tomorrow.
## When to Use
Run this at the end of your work day, before you close the laptop.
Run this before closing the laptop at the end of the workday.
## Instructions
1. Review today's completed work (check completed tasks, calendar events that happened, any notes from the day).
2. Check what's still outstanding — anything started but not finished, items that slipped.
3. Preview tomorrow's schedule (if calendar MCP is connected).
4. Produce a shutdown summary.
### Output Format
**Shutdown — [Date]**
**Completed Today**
[What got done. Brief list.]
**Still Outstanding**
[What didn't get finished. Note anything that needs attention tomorrow.]
**Tomorrow's Preview**
[Tomorrow's calendar events and any deadlines. If no calendar connected, note it.]
**Open Loops**
[Anything you mentioned today that needs follow-up but isn't a specific task yet. Ideas to capture, people to contact, things to look into.]
## Customization Ideas
As you use this, consider adding:
- A reflection prompt ("What went well today?")
- A journaling step
- A review of your Drafts inbox (to clear anything captured during the day)
- Priority-setting for tomorrow
The assembler in Video 7 will help you customize this to your actual needs.
## Rules
- Keep it brief. This is a closing ritual, not a project.
- The goal is peace of mind: nothing forgotten, tomorrow previewed.
- If information is missing (no calendar, no task list), work with what's available.
- Never create new tasks during shutdown unless the user asks. Just surface what exists.
Work through these four steps in order. Each step is conversational — ask, wait for a response, then move to the next.
---
*Started with the Robot Assistant Field Guide Starter Kit. Customized in Video 7 via the assembler.*
### Step 1: Accomplishments
Read `~/notes/todo.md` and identify any tasks that were completed today (or ask Connor what he got done if the file doesn't reflect completions clearly).
Present what was accomplished:
**Completed Today**
[List of tasks finished. If nothing is marked done, ask: "What did you get done today?"]
---
### Step 2: Victory Lap
Say something like:
> "Time for the victory lap. What's one thing that went well today — something worth remembering?"
Wait for a response. Acknowledge it briefly (one sentence, no filler).
Then say:
> "Don't forget to record that as a voice journal note."
---
### Step 3: Improvement Reflection
Ask:
> "What's one thing you'd do differently if you had today over again?"
Wait for a response. Acknowledge it briefly. No need to problem-solve or offer advice unless asked.
---
### Step 4: Plan Tomorrow
Say:
> "Let's plan tomorrow. What tasks do you want to tackle?"
Take their input and update `~/notes/todo.md` with tomorrow's tasks. Add a date marker or "tomorrow" label so they're easy to find in the morning briefing.
**Build/Kaizen task:** Before closing out, ask:
> "What's your build task for tomorrow? One thing that will make you more productive in the future."
Add it to todo.md labeled as `[build]`.
---
## Rules
- Never skip the victory lap. It's the most important step.
- Keep the whole routine under 10 minutes. If a step is going long, gently redirect.
- Don't create tasks beyond what Connor asks for. Just capture what he says.
- Always end with the build/kaizen task. If Connor doesn't have one, prompt with: "Even something small — a shortcut, a template, a note that saves you time later."
- Write tasks to todo.md, don't just echo them back.
---
*Customized in Video 7 via the assembler.*

130
weekly-review/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: weekly-review
description: A weekly check-in workflow that reviews the past week, scans what's ahead, and produces a summary with priorities.
description: Single weekly session (typically Sunday) that reviews the closing week and plans the new one. Creates a week note for the new week at the end.
triggers:
- weekly review
- how'd my week go
@ -10,65 +10,87 @@ triggers:
# Weekly Review
Step back, look at the week, and plan the next one.
One session does it all: close out the week, reflect, and plan the next one.
## When to Use
Run this once a week — Sunday evening, Monday morning, or whenever works for your rhythm.
Run this on Sunday (or Saturday if Sunday is busy). Do both parts in a single session.
## Week Note File Naming
Week notes live at `~/notes/week_YYMMDD.md` where YYMMDD is the date of that week's **Monday**.
Example: a week starting Monday April 7, 2026 → `~/notes/week_260407.md`
## Instructions
### Step 1 — Gather
1. Check this week's calendar events (if calendar MCP is connected).
2. Review completed tasks or projects from the week.
3. Scan any notes, journal entries, or captured items from the past seven days.
### Step 2 — Review
1. Summarize what happened this week: key events, completed work, progress made.
2. Identify what's still open: tasks that didn't get finished, items that slipped.
3. Flag anything overdue or time-sensitive.
### Step 3 — Reflect
Ask the user:
- How did the week go overall?
- What went well?
- What needs attention next week?
- Anything you want to change or adjust?
### Step 4 — Output
Produce a formatted weekly summary:
**Weekly Review — [Date Range]**
**What Happened**
[Key events, accomplishments, completed work.]
**Still Open**
[Unfinished items, slipped tasks, things that need attention.]
**Next Week**
[Upcoming calendar events, deadlines, priorities.]
**Reflections**
[The user's notes on how the week went and what to adjust.]
## Customization Ideas
This is a starter weekly review. As you use it, consider adding:
- Role-based review (how did each area of your life/work get attention?)
- Goal tracking (progress toward monthly or quarterly goals)
- A journaling step that gets saved to a long-term record
- Automated data gathering from connected tools
The assembler in Video 7 will help you customize this to your actual workflow and connected tools.
## Rules
- The reflection step is conversational — ask questions and let the user respond. Don't skip it or auto-fill it.
- Keep the output scannable. Short lines, clear sections.
- If data sources aren't connected, work with what's available. A review based on the user's verbal summary is still valuable.
- Save the output to the workspace so it becomes a record over time.
Work through the two parts in order.
---
*Started with the Robot Assistant Field Guide Starter Kit. Customized in Video 7 via the assembler.*
### Part 1: Review the Closing Week
1. Find this week's note at `~/notes/week_YYMMDD.md` (current week's Monday date).
2. Read the goals/tasks that were set for the week.
3. Read `~/notes/todo.md` to check what got done.
4. Present a summary:
**Week in Review — [Week of Month Day–Month Day]**
**Goals This Week**
[The goals/tasks set in the week note at the start of the week.]
**Accomplished**
[What got done. Cross-reference the week note goals with todo.md completions.]
**Incomplete**
[Goals that didn't get finished. No judgment — just facts.]
**Carry Forward?**
Ask: "Anything from this week you want to carry into next week?"
5. Ask two reflection questions (conversational — wait for each answer):
- "How did the week go overall?"
- "Anything you'd do differently next week?"
---
### Part 2: Plan the New Week
1. Calculate the upcoming Monday's date.
2. Create `~/notes/week_YYMMDD.md` for the new week using the template below.
3. Ask: "What are your goals for this week? What tasks do you want to make sure happen?"
4. Take the response and populate the Goals section of the new week note.
5. Ask: "Anything else to note going into the week? Deadlines, commitments, things to watch for?"
6. Add those to the Notes section.
---
## Week Note Template
```markdown
# Week of [Month Day–Month Day, Year]
## Goals
[Weekly goals and tasks — what Connor wants to accomplish this week.]
## Notes
[Deadlines, commitments, context, things to watch for this week.]
## Reflection
[Filled in at the end of the week during the weekly review.]
```
---
## Rules
- Always do both parts. Don't let the session end without creating the new week note.
- The reflection questions are conversational — ask them, wait, don't skip or auto-fill.
- If this week's note doesn't exist (e.g., it was never created), work from todo.md and ask what the goals were.
- Carry-forward tasks should be added to todo.md, not just mentioned.
- Keep the whole session focused. If it's running long, it's okay to timebox the planning step.
---
*Customized in Video 7 via the assembler.*