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

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