From grimoire
Sets artificial deadlines at 50-70% of available time to force focus, eliminate perfectionism, and prevent scope creep. Useful when tasks expand beyond reasonable effort.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:apply-parkinson-lawThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Set artificial deadlines shorter than available time to force focus, eliminate gold-plating, and prevent work from expanding to fill the time you give it.
Set artificial deadlines shorter than available time to force focus, eliminate gold-plating, and prevent work from expanding to fill the time you give it.
Adopted by: C. Northcote Parkinson observed the law in British civil service (1955); it was later applied to knowledge work by Tim Ferriss in The 4-Hour Workweek (2007) and is standard in agile sprint methodology. Fixed-length sprints exist precisely because unbounded time inflates scope.
Impact: In a classic experiment, students given 3 hours for an assignment produced work of equal or better quality than students given 1 week, while investing a fraction of the time (Ariely & Wertenbroch, 2002). Artificial deadlines compress decision-making and eliminate the perfectionism that consumes marginal hours.
Why best: Most work has a natural point of "good enough" that arrives well before the available deadline. The surplus time is spent on diminishing-returns polishing, second-guessing, and scope creep. Imposing a shorter deadline forces the question: "What is the minimum viable version of this?"
For any task or project:
If the task is due Friday and it's Monday, commit to finishing by Wednesday. The 2 spare days become a quality buffer — not working time.
Parkinson's Law inflates scope because "done" is vague. Before starting any task, write one sentence defining what done looks like:
# BAD (vague, expands indefinitely)
"Work on the report"
# GOOD (terminates clearly)
"Report has an executive summary, 3 data charts, and a recommendations section —
max 4 pages, reviewed once for typos"
Without a definition, done never arrives.
For tasks without fixed external deadlines, impose time limits in advance:
| Task type | Default timebox |
|---|---|
| Email triage | 20 minutes, twice per day |
| Meeting prep | 15 minutes |
| First draft of any document | 60–90 minutes |
| Code review | 45 minutes |
| Research / investigation | 90 minutes, then commit to a conclusion |
Set a visible timer. When it expires, ship what you have or explicitly decide to extend — but the extension must be a conscious choice, not drift.
For projects spanning days or weeks:
If the project is 6 weeks: week 2 = prototype, week 4 = review draft, week 6 = final. The intermediate deadlines prevent everything from piling up in week 6.
Common ways work expands to fill time:
When the timebox expires, name the expansion behavior explicitly: "I am polishing, not finishing." Then stop.
Email: Limit to two 20-minute blocks per day. The constraint forces you to batch, prioritize, and write concisely. Unlimited email access expands to fill all available time.
Sprint planning: 2-week sprints exist because unbounded projects balloon. The sprint deadline forces the team to commit to scope and prevents infinite refinement.
First draft: Give yourself 60 minutes to write a rough first draft. The resulting draft is usually 80% of the final quality at 20% of the time a "take as long as needed" approach would consume.
Setting deadlines without a done definition: An arbitrary deadline on a vague task produces rushed, incomplete work. Define done first, then compress the timeline.
Cutting the deadline so aggressively that the work is genuinely incomplete: 50–70% of natural time, not 10%. Parkinson's Law compresses padding; it does not eliminate necessary work.
Applying it to safety-critical or high-precision work: Architectural decisions, security reviews, and medical documentation should not be rushed to save time. Apply elsewhere.
Not protecting the reclaimed time: If you finish in 3 days instead of 5, that surplus is value only if it isn't immediately filled with new low-priority tasks.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireCombines Pareto prioritization (80/20), timeboxing, and deep work techniques to manage attention, eliminate context-switching, and maximize high-impact output. Useful for time management, combating procrastination, and planning schedules.
Identifies the single most important or dreaded task each day and completes it first, before email or meetings. Use when planning a workday or session to eliminate procrastination.
Triages tasks and brain dumps using Eisenhower matrix into DO, SCHEDULE, DELEGATE, ELIMINATE quadrants. Applies rules for prioritization, deadlines, and conversion to actionable items.