Resume Day
Resume a working session. Quick morning check-in to restore context.
Check-in Steps
- •
Working Memory - Already auto-loaded from
.claude/context/working-memory.md. Review it for context. - •
Diary - Read today's diary file. If it doesn't exist, create it from yesterday's template.
- •
Last session - What was I working on? Any incomplete tasks or actions?
- •
Task DB - Check tasks using the CLI:
- •
.claude/skills/task-cli/scripts/task-cli.sh today— tasks due today or with today's attention date - •
.claude/skills/task-cli/scripts/task-cli.sh overdue— overdue tasks - •
.claude/skills/task-cli/scripts/task-cli.sh checkins— tasks with check-ins due (these are also "today's tasks") - •
.claude/skills/task-cli/scripts/task-cli.sh routines due— today's routines - •
.claude/skills/task-cli/scripts/task-cli.sh activity --limit 20— recent activity to see what happened since last session
- •
- •
Projects - Check working memory for blockers or urgent items.
- •
Email & Calendar Review — Check schedule and inbox per the google skill (@.claude/skills/google/SKILL.md):
- •
.claude/skills/google/scripts/google-cli.sh calendar today - •
.claude/skills/google/scripts/google-cli.sh gmail search "category:primary in:inbox newer_than:2d" - •Read specific emails with
gmail get MESSAGE_ID
Identify: today's meetings, urgent items, replies updating tasks, new action items.
Propose changes, don't make them — summarise findings and use
AskUserQuestionbefore creating/updating tasks. - •
- •
Project README Check — For each project with recent email activity or task changes, check if the README's
<!-- AI_STATUS_START -->block is current. Propose updates if stale.
Output
Provide a quick summary:
- •What was done earlier today (if anything)
- •What's outstanding for today (include check-ins!)
- •Any urgent items needing attention
- •Suggested next action
Keep it concise - this is a quick check-in, not a full summary.