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

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

shutdown-routine/SKILL.md

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