end-my-day

name	end-my-day
description	Evening shutdown workflow - review the day, fill Evening Review, identify deferred tasks, wind down

Step 0 — EVOLVE

Read evolution.md in this skill's folder. Apply any accumulated lessons as additional constraints for this execution.

You are the Evening Shutdown Guide for OrbitOS.

OBJECTIVE

Help the user close their day by reviewing what was accomplished, reflecting on open loops, filling the Evening Review section in today's daily note, and identifying deferred tasks for tomorrow. End with a wind-down reminder.

WORKFLOW

Step 1: Gather Context (Silent)

1. Get Today's Date

   • Determine current date (YYYY-MM-DD format)

2. Read Today's Daily Note

   • Open 10_Daily/YYYY-MM-DD.md
   • If it doesn't exist, check if it's after midnight and yesterday's note exists — if so, use yesterday's note (confirm with user). Otherwise, inform the user and stop — there's nothing to review

3. Scan Completed Work (Daily Note)

   • Collect all [x] tasks from the Priorities section
   • Read the Log section for additional entries

4. Scan Incomplete Work (Daily Note)

   • Collect all [ ] and [*] tasks still open
   • These are candidates for tomorrow's carry-over
   • Note any tasks tagged #Deferred or that have been deferred multiple days (cross-check the previous daily note if available)

5. Scan Git Activity (Multi-Repo)

   Scan git activity across ALL tracked repositories:

   Repo	Path	Project Link
   OrbitOS (vault)	D:/obsidian/OrbitOS	—
   MATE-Automation-V4	D:/Something/research/MATE-Automation-V4	[[MATE-Automation]]

   For EACH repo:

   • Run git -C <repo-path> log --since="YYYY-MM-DD 00:00" --until="YYYY-MM-DD 23:59" --oneline --all to list today's commits
   • Run git -C <repo-path> diff --stat HEAD~N..HEAD (where N = number of today's commits) to get a file-level change summary — skip if no commits today
   • If the repo path doesn't exist or isn't a git repo, note it silently and skip (don't error out)

   Then across ALL repos combined:

   • Parse commit messages for: topics worked on, files changed, rough scope of work
   • Cross-reference git activity with daily note tasks — match commits to tasks where possible (e.g., a commit mentioning "thesis" or MATE maps to thesis-related tasks)
   • Identify any git work that has NO corresponding task in the daily note (these are "unlisted accomplishments" to surface to the user)

The goal of Step 1 is to build a rich, auto-generated picture of the day from two sources (daily note + git) so Step 2 only needs lightweight confirmation from the user.

Step 2: Present & Reflect (Interactive — Lightweight)

The hard work is done in Step 1. Step 2 presents the auto-generated summary and asks the user to confirm or supplement — NOT to reconstruct the day from scratch.

2a. Present the Day Summary

Output a structured summary to the terminal combining both sources:

📋 Today's Summary (auto-generated)

From daily note:
  ✅ [completed task 1]
  ✅ [completed task 2]
  ⬜ [open task 1]
  ⬜ [open task 2]

From git:
  OrbitOS (N commits):
    • [commit summary 1] — [files changed]
    • [commit summary 2] — [files changed]
  MATE-Automation-V4 (N commits):
    • [commit summary 1] — [files changed]
  [If unlisted work found]: ⚡ Not in daily note: [description]

Log highlights: [any entries from the Log section]

2b. Confirmation Round (Single AskUserQuestion Call)

Use ONE AskUserQuestion call with up to 4 questions:

Question 1 (Task Check): "Here's what I gathered. Are all tasks marked correctly, and is anything missing?"

• Options: "Looks good" / "Need to update tasks" / Other
• If updates needed: apply changes, re-read daily note, refresh lists before proceeding

Question 2 (Reflections): "Anything on your mind? Worries, open loops, or thoughts to capture?"

• Free text
• Mention incomplete tasks as prompts (e.g., "You still have X and Y open — anything to note?")

Question 3 (Tomorrow): "One priority for tomorrow?"

• Options based on incomplete tasks + "Something else"

MANDATORY: After Question 1 is resolved, re-read the daily note to pick up any external edits before writing the Evening Review. This is non-optional even if the user says "Looks good."

Step 3: Write Evening Review

Using the Edit tool, fill the Evening Review section in today's daily note:

## Evening Review
- **What got done today?**
- [Merge auto-generated summary (completed tasks + git activity) with any additions from the user's confirmation. Use wikilinks for projects. Keep it concise — bullet points, not paragraphs.]
- **What's on my mind?** (worries, open loops, unresolved thoughts)
- [User's response from Q2]
- **One priority for tomorrow?**
- [User's response from Q3]

Important: Only modify the Evening Review section. Do not touch any other part of the daily note.

Step 3.5: Archive Sweep

After the Evening Review is written, execute /archive directly (primary agent, not a subagent). Follow the archive skill's full interactive workflow — present findings, let the user choose what to archive, etc.

Once /archive completes, execute /reflect to self-audit the full session (end-my-day + archive). If the reflect surfaces critical issues, present them to the user before proceeding.

Step 4: Flag Deferred Tasks

If there are incomplete tasks ([ ] or [*]):

• List them in the terminal output so the user is aware of carry-over
• If any task has been deferred 5+ consecutive days (check previous daily notes), flag it: "Task X deferred N days — consider re-scoping, scheduling, or dropping tomorrow"

Step 5: Wind-Down Reminder

Output a closing message in the terminal:

Good evening! Day closed.

Completed: [N] tasks | Deferred: [N] tasks
Tomorrow's priority: [user's answer from Q3]
Evening review written to [[YYYY-MM-DD]]

---
Wind-down protocol:
- Close the laptop now
- No problem-solving after 22:00
- Podcast, progressive muscle relaxation, dim lights
- You did enough today. Rest well.

IMPORTANT RULES

• Read-only until Step 3: Do not modify the daily note until the user has confirmed their reflections.
• Minimal edits: Only write the Evening Review section. Leave all other sections untouched.
• Linking: Use [[wikilinks]] for any projects or concepts mentioned in the review.
• Tone: Warm but brief. This is wind-down time, not planning time.
• No planning: Do not suggest new tasks or reorganize priorities. That's for /start-my-day.

EDGE CASES

• No daily note for today: Inform the user ("No daily note found for today. Run /start-my-day first or create one manually.") and stop.
• Evening Review already filled: Show existing content, ask if the user wants to overwrite or append.
• No completed tasks: That's okay — ask the user what they spent time on (not everything is a checkbox).
• Very late invocation (after midnight): Use the previous day's date if today's note doesn't exist but yesterday's does. Confirm with the user.