AGENT SKILL

ams-deep-work-planner

暂无简介

License 许可
MIT
所属仓库
TanNhatCMS/jarvis
最近更新
2026-11-07
Stars
★ 0
Forks
1

03 SKILL.md 正文

Deep Work Planner

Overview

Deep work = cognitively demanding tasks done in distraction-free concentration. It's where valuable output comes from — and it's incompatible with a fragmented calendar.

Shallow work (email, admin, meetings) expands to fill all available time unless deep work is scheduled first.

Planning deep work means: choosing the right tasks, blocking the time, designing the environment, and defending the blocks.

When to use

  • Important projects stall while email and meetings consume days
  • Wanting a sustainable routine of focused creative work
  • Knowledge workers feeling busy but unproductive
  • Designing team norms that protect maker time
  • Students or researchers needing long thesis/writing blocks

Core concepts

  • Deep vs. shallow. Deep: cognitively demanding, creates new value, hard to replicate. Shallow: logistical, easy to replicate, necessary but not valuable. Audit your week by this split.
  • Time blocking. Deep work gets calendar blocks — 90+ minutes, ideally 2-4 hours. Unscheduled deep work doesn't happen; shallow work is the default.
  • Task selection. Not all hard tasks deserve depth. Choose: high-leverage, deadline-meaningful, requiring sustained thought. One deep task per block.
  • The shutdown ritual. End-of-day complete shutdown: review, capture open loops, close everything. Protects evenings and makes mornings start clean.
  • Attention residue. Switching tasks leaves mental residue that degrades the next task. Single-task blocks + real breaks beat 'multitasking.'
  • Depth metrics. Track deep hours per week and per project. What gets measured gets protected. 10-15 deep hours/week is excellent for most roles.
  • Energy alignment. Schedule deep blocks in peak energy (usually morning). Guard the golden hours; shallow work fills the troughs.
  • Boredom tolerance. Deep work requires tolerating boredom without reaching for the phone. This is trainable — start with 50-min blocks and extend.

Practical workflow

  1. Audit the week. Classify last week's hours: deep vs. shallow. Most find <5 deep hours. That's the baseline to beat.
  2. Choose deep tasks. List this week's 2-3 highest-leverage cognitively-demanding tasks. These earn the blocks; everything else is shallow.
  3. Block 3-5 sessions. 90-180 min blocks, mornings preferred, on the calendar as unmovable commitments. Start with 3/week; build up.
  4. Design the environment. Phone out of room, notifications off, door closed / status set, materials ready. Friction against distraction, not willpower.
  5. Define block protocol. One task per block, timer optional, scratch pad for intrusions, break after. Same ritual every time builds the habit.
  6. Run the shutdown ritual. End of day: 10 min to close loops, plan tomorrow's first block, shut down completely. No 'quick checks' after.
  7. Track depth weekly. Log deep hours per block. Review: total, per project, interruptions. Trend matters more than any single week.
  8. Defend and expand. Treat blocks like client meetings. Quarterly: can you add one more block? Can meetings move off golden hours?

Common pitfalls

  • Scheduling but not defending. Blocks that every 'urgent' request overrides. An undefended block teaches everyone it's fake. Defend or delete.
  • Too-ambitious start. Five 3-hour blocks in week one. Start with 2-3 ninety-minute blocks; build the muscle before the marathon.
  • Wrong tasks in blocks. Deep blocks spent on email triage. Blocks are for the 2-3 chosen deep tasks only — ruthlessly.
  • Phone in the room. 'On silent, face down' still tempts and still interrupts (vibration, screen glow). Out of the room, or it doesn't count.
  • Skipping the shutdown. Evenings bleed into work, mornings start groggy. The shutdown ritual is what makes deep work sustainable.
  • Measuring only hours. 4 'deep' hours of distracted half-work. Honest focus matters more than clock time — pair with interruption logging.
  • All depth, no shallow time. Deep blocks with no scheduled shallow time means shallow tasks invade the blocks. Schedule admin/email windows too.
  • Ignoring energy. Deep blocks at 4pm for a morning person. Align with chronotype or fight biology every session.

04 同仓库更多 Skills

TanNhatCMS
TanNhatCMS/jarvis

web-scrape

Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

design-taste-frontend

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

★ 0
TanNhatCMS
TanNhatCMS/jarvis

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

★ 0
TanNhatCMS
TanNhatCMS/jarvis

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

★ 0
TanNhatCMS
TanNhatCMS/jarvis

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

★ 0
TanNhatCMS
TanNhatCMS/jarvis

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).

★ 0