evening shutdown

The problem

Developers often end their day with a vague sense of "stuff done" but no concrete record of progress or verified submissions. This lack of closure creates decision friction the following morning, wasting the first hour of work on re-orientation.

What it does

• Performs completion verification on today's claimed tasks to ensure work was actually submitted or merged.
• Syncs Google Calendar events to compare scheduled tasks against reality.
• Generates a structured evening log capturing financial events, new intel, and carry-over items.
• Sets a single, non-negotiable "First Move" for the next morning based on urgency and deadlines.
• Updates memory flags and persistence layers to maintain project context across sessions.

Why this beats prompting it yourself

Manually reflecting on the day usually results in optimistic bias or forgotten details. This skill enforces a strict verification protocol and automated calendar cross-referencing that resists human forgetfulness, ensuring your "done" list is actually done.

Use cases

• Transitioning from deep work to shutdown without leaving open loops.
• Verifying PR merges or deployment confirmations before logging off.
• Automating the hand-off between today's session and tomorrow's morning routine.
• Maintaining a high-fidelity audit trail of work for standups or reporting.

Known limitations

Requires access to Google Calendar via gcal_list_events for landscape mapping. Verification depends on the AI's ability to access the specific platforms where tasks were performed.