Morning Pack

Context switching and inbox triage eat the first hour of every productive day. This skill eliminates the manual assembly of tasks and messages by scanning your local workspace, connected calendars, and email to build a single, high-signal briefing file. It turns your morning into a "read, decide, copy, send" workflow so you can stay in deep work instead of hunting for what is due.

What it does

• Inbox Triage scans email threads and local files to identify who has the next move on open items.
• Deep Work Scheduling blocks out specific hours for high-intent tasks based on your peak cognitive times.
• Draft Staging generates ready-to-copy follow-up messages and nudges based on your personal voice guidelines.
• Status Tracking builds comparative tables of who you are waiting on and who is waiting on you, including aging metrics.
• Daily Board Assembly pulls fixed-time events, due dates, and pending decisions into one markdown file.

How it works

1. Initialize Settings by running the /morning-pack command to define work hours, file locations, and notification thresholds.
2. Context Scanning reads your task lists, calendar, recent emails, and memory files to establish today's state of play.
3. Follow-up Sweep flags silent threads and generates draft responses for any items past your defined response window.
4. Pack Generation saves a dated markdown file to your designated folder, organized by energy levels and priority.

Frameworks & tools

This skill works with local files, git repositories, and connected email/calendar APIs. It integrates with Claude Code or Cursor workspaces and uses standard Markdown for all staging and reporting.

Why this beats prompting it yourself

Generic prompts often invent dates or miss the nuances of silent threads across multiple files. This skill enforces strict source-checking and energy-based scheduling, ensuring your day is ordered by your best thinking hours rather than a random list of chores.

Use cases

• Start the day with a pre-prioritized list of deep work and staged replies.
• Track overdue responses from clients or team members across disjointed email threads.
• Maintain a daily record of project status without manual data entry.
• Ensure recurring weekly tasks never slip through the cracks on the right day.

Known limitations

Does not send messages or emails directly. Relies on local file access and active connections to external accounts for full functionality. Requires an initial setup of a settings file.