---
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 today` to see what was on the plate for today, then ask Connor what he got done.

Present what was accomplished:

**Completed Today**
[List of tasks Connor confirms finishing. Mark each done with `vik task update <ID> --done`.]

---

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

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:** Before closing out, ask:

> "What's your build task for tomorrow? One thing that will make you more productive in the future."

Add it with `vik task create "Task title" d+1 --label 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."
- Create tasks in Vikunja with `vik task create`, don't just echo them back.

---

*Customized in Video 7 via the assembler.*