Structure the week so deep work, admin, and recovery each get real space. Protect capacity on purpose—every unplanned yes borrows from something that mattered.
When to Use
The calendar is full but outcomes feel thin, or you keep underestimating how long work takes.
You need a repeatable way to batch work and match effort to your energy.
Workflow
Time-blocking: assign calendar blocks to types of work (deep, meetings, admin), not just meetings.
Batching: group similar tasks (email, errands, shallow tickets) to cut switching cost.
Energy mapping: place the hardest thinking in your highest-energy hours; put shallow work in lows.
Parkinson's law: give tight, explicit time boxes so work does not expand without bound.
Buffer allocation: never schedule 100%—hold ~20% for surprises, slippage, and recovery.
Planning fallacy: pad estimates; assume important work runs long the first time.
Weekly over daily: one weekly pass (themes + big rocks) beats reactive daily triage alone.
Say no to protect yes: decline or defer what does not fit the plan; name the trade explicitly.
Examples
Example 1: You have three big deliverables—block deep work in morning peaks, batch Slack/email after lunch, leave Friday afternoon empty for overflow.
Example 2: A stakeholder adds a “quick” project—show the calendar blocks it displaces and negotiate scope or timing instead of stacking blindly.
1---2name: time-management3description: Time Management4---5# Time Management67Structure the week so deep work, admin, and recovery each get real space. Protect capacity on purpose—every unplanned yes borrows from something that mattered.89## When to Use10- The calendar is full but outcomes feel thin, or you keep underestimating how long work takes.11- You need a repeatable way to batch work and match effort to your energy.1213## Workflow141. **Time-blocking**: assign calendar blocks to *types* of work (deep, meetings, admin), not just meetings.152. **Batching**: group similar tasks (email, errands, shallow tickets) to cut switching cost.163. **Energy mapping**: place the hardest thinking in your highest-energy hours; put shallow work in lows.174. **Parkinson's law**: give tight, explicit time boxes so work does not expand without bound.185. **Buffer allocation**: never schedule 100%—hold ~20% for surprises, slippage, and recovery.196. **Planning fallacy**: pad estimates; assume important work runs long the first time.207. **Weekly over daily**: one weekly pass (themes + big rocks) beats reactive daily triage alone.218. **Say no to protect yes**: decline or defer what does not fit the plan; name the trade explicitly.2223## Examples24**Example 1:** You have three big deliverables—block deep work in morning peaks, batch Slack/email after lunch, leave Friday afternoon empty for overflow.2526**Example 2:** A stakeholder adds a “quick” project—show the calendar blocks it displaces and negotiate scope or timing instead of stacking blindly.
Run npx skillmds@latest add sethdford/time-management in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Time Management It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
sethdford (@sethdford) published this skill. Their other Agent Skills are listed on their SkillMD profile.