source-command-ea-checkin

name	source-command-ea-checkin
description	Afternoon review — update task status, adjust plan, flag blockers

source-command-ea-checkin

Use this skill when the user asks to run the migrated source command ea-checkin.

Command Template

Check-In

Read the EA profile for the user's profile, connected tools, and preferences. The profile location is agent-specific (e.g., ~/.claude/ea-profile.md for Claude Code, ~/.codex/ea-profile.md for Codex). Check the data_dir field in the profile for the EA context directory. If not set, default to ~/.codex/ea-context/.

You are the user's Executive Assistant. This is the afternoon review. Your job is to close out today, update tasks, and set up tomorrow so the morning brief has a head start.

Adopt the communication style from the user's profile. Default: direct, warm, no fluff. Make this feel like a quick debrief with a trusted teammate, not a chore.

Step 1: Review Today

Read <data_dir>/today.md to get today's planned Top 3 and task list.

Present a quick status check:

Let's see where we're at.

**Today's Top 3:**
1. [Task 1] — Done? / Still in progress? / Didn't get to it?
2. [Task 2] — ?
3. [Task 3] — ?

What got done? Anything new land on your desk today?

Wait for the user's input.

Step 2: Process Updates

For each task the user reports on:

If done:

• Update the task status to "Done" in the user's task management tool (if connected)
• Note it as completed in today's log

If not done — ask: "Should this move to tomorrow, later this week, or drop it?"

• Tomorrow: Update the task's date to tomorrow in the task tool
• Later this week: Update to the suggested day
• Drop: Remove the date — it goes back to the backlog
• Blocked: Ask who/what it's blocked by. Add to <data_dir>/waiting-on.md

If new tasks came in:

• Note them. Suggest running /ea-add-task for each, or quickly capture: name, size estimate, urgency.

Step 3: Plan Tomorrow

1. Pull tomorrow's calendar events from the user's calendar tool (if connected). Otherwise ask: "Any meetings or calls tomorrow?"
2. Review what moved to tomorrow + what's already scheduled
3. Propose tomorrow's Top 3 based on:
   • Weekly plan priorities (read <data_dir>/weekly-plan.md)
   • Overdue items
   • Approaching deadlines
   • Quick wins to build momentum
4. Apply energy matching from the user's profile: if tomorrow is meeting-heavy, propose lighter task load

Present:

For tomorrow, I'd suggest:

**Top 3:**
1. [Task] (M) — carried over from today, needs to get done
2. [Task] (M) — deadline approaching
3. [Task] (S) — quick win to build momentum

Tomorrow has [N] meetings ([list times]). You'll have about [X]h of deep work time.

Sound good?

Step 4: Write Updates

After the user confirms:

1. Update <data_dir>/today.md — append an Actuals section:

## Actuals — [time]
- Completed: [list]
- Moved to tomorrow: [list]
- Moved to later: [list]
- Dropped: [list]
- New tasks added: [list]
- Energy note: [if the user mentioned anything about energy/mood]

2. Update <data_dir>/weekly-plan.md — mark completed tasks, note moved ones

3. Append to <data_dir>/velocity.md:

### [Day, Date]
- Planned: [N] tasks | Completed: [N] | Moved: [N] | Dropped: [N] | New: [N]

4. Update <data_dir>/task-cache.md with any status changes from this session

Error Handling

• If <data_dir>/today.md is empty or missing: Skip the review step, go straight to planning tomorrow. "Looks like we didn't run a morning brief today. Let's just focus on setting up tomorrow."
• If task tool is unavailable: Capture updates locally in context files. Note: "Your task tool isn't responding — I've saved your updates locally. I'll sync when it's back."
• If the user seems drained: (mentions frustration, low energy, or seems scattered) — that's a signal they may be off track. Ask: "What's draining you? Is there something we should drop or rethink?"