---
name: shutdown-routine
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
  - close out the day
  - shutdown
---

# Shutdown Routine

Close the loop. Review the day, capture wins, reflect on improvements, and set up tomorrow.

## When to Use

Run this before closing the laptop at the end of the workday.

## Instructions

Work through these four steps in order. Each step is conversational — ask, wait for a response, then move to the next.

---

### Step 1: Accomplishments

Run `vik task done` to see what was completed today. Present the output:

**Completed Today**
[Output from vik]

---

### 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:

> "Is there anything you could have done better today?"

If the user gives you an answer for what could have been improved, then add their reply to the user's journal with: `$HOME/notes/skills/shutdown-routine/scripts/add_improvement_journal_entry "USER'S REPLY"`

If the user responds that nothing needed improvement from today, ask this follow-up question

> "How would you like to raise the bar?"

Then enter the user's reply into tomorrow's daily note. (filename dn_yymmdd.md where yymmdd is tomorrow's date)

Put their ansewr into this part of the file:
```md
# Today I *get* to
raise the bar: USER'S REPLY
## meetings
```

---

### Step 4: Plan Tomorrow

Run `vik task upcoming --days 1` to show what's already on the schedule for tomorrow. Present the results:

**Already scheduled for tomorrow:**
[Output from vik]

Then ask:

> "What else do you want to tackle tomorrow?"

Take their input and create each task with `vik task create "Task title" d+1` so they show up in tomorrow's briefing.

**Build/Kaizen task:** Check the `vik task upcoming --days 1` output (already fetched above) for any task with a `kz` label.

- **If a kz task is already scheduled for tomorrow:** Say something like: "Your build task tomorrow is already set: [task title]." No further action needed.
- **If no kz task is scheduled for tomorrow:** Run `vik task list --label kz` and present the output, then ask: "Which of these do you want as your build task tomorrow?" Once Connor picks one, schedule it with `vik task update <ID> --due d+1`.

---

## Rules

- Never skip the victory lap. It's the most important step.
- 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."
- Create tasks in Vikunja with `vik task create`, don't just echo them back.
