parkinsons-law
Skill6 starsChanged 34 days agoMITView on GitHub
Apply Parkinson's Law when discussing project planning, sprint duration, deadline setting, scope creep, or why work seems to expand no matter how much time is allocated. Trigger on phrases like "we always use up all the time we're given", "if we give the team a month they'll take a month", "why does scope keep growing?", "should we set tighter deadlines?", or any discussion about the relationship between available time and how long work takes. Parkinson's Law is a universal phenomenon in project management.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- SidekicksStudio/fhww-skillstheir own version, first seen May 6, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- SidekicksStudio/fhww-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository79 other files it gives its agents.
- adr-phase-coverageSkill
- aposd-red-flag-reviewSkill
- apple-on-device-aiSkill
- artifact-gatesSkill
- asc-app-create-uiSkill
- asc-build-lifecycleSkill
- asc-cli-usageSkill
- asc-crash-triageSkill
- asc-id-resolverSkill
- asc-localize-metadataSkill
- asc-metadata-syncSkill
- asc-notarizationSkill
- asc-ppp-pricingSkill
- asc-release-flowSkill
- asc-revenuecat-catalog-syncSkill
- asc-shots-pipelineSkill
- asc-signing-setupSkill
- asc-submission-healthSkill
- asc-subscription-localizationSkill
- asc-testflight-orchestrationSkill
- asc-wall-submitSkill
- asc-workflowSkill
- asc-xcode-buildSkill
- choose-boring-technologySkill
- ci-preflightSkill
- conways-lawSkill
- cost-routingSkill
- cost-tier-routingSkill
- cunninghams-lawSkill
- ddd-strategic-auditSkill
- ddd-tactical-reviewSkill
- debug-test-captureSkill
- developing-ios-appsSkill
- doerrs-lawSkill
- fitts-lawSkill
- fix-regression-guardSkill
- galls-lawSkill
- goodharts-lawSkill
- greenspuns-tenth-ruleSkill
- gsd-core-hooksSkill
- hofstadters-lawSkill
- hyrums-lawSkill
- ios-accessibilitySkill
- ios-simulator-boot-healthSkill
- kerckhoffs-principleSkill
- kernighans-lawSkill
- knuths-optimization-principleSkill
- lady-lovelaces-objectionSkill
- leaky-abstractionsSkill
- linuss-lawSkill
- mobile-ios-designSkill
- money-boundary-judgmentSkill
- moores-lawSkill
- no-deferSkill
- norvigs-lawSkill
- peter-principleSkill
- postels-lawSkill
- post-fix-traceSkill
- qa-test-architectSkill
- rubber-duckSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Effort adjusts to perceived time available: If you have a week, you approach a problem as a week-long problem.
- Distinctive: line 30
When you want a decision made, a design drafted, or a prototype built, giving less time forces prioritization.
- Distinctive: line 33
Instead of "deliver feature X completely," try "spend two weeks on X and ship whatever is done." Time-boxing forces prioritization within …
- Distinctive: line 53
If we cut the deadline in half, what would we cut from scope?
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Parkinson's Law
"Work expands so as to fill the time available for its completion." — Cyril Parkinson, 1955
The core idea
Given more time to complete a task, people use it — through more elaborate solutions, more polishing, more scope, more second-guessing, or simply slower pace. The work doesn't have a fixed duration; it stretches to fill whatever container you give it.
Parkinson observed this originally in bureaucracies (a report that could be done in one day takes three when three are allocated), but the pattern is universal in knowledge work.
Why it happens
Effort adjusts to perceived time available. If you have a week, you approach a problem as a week-long problem. If you have a day, you find the 80% solution that matters.
Scope expands with available time. Extra time rarely stays empty — people find adjacent improvements, additional polish, more edge cases to handle, more documentation to write. This isn't laziness; it's often genuine value-adding activity. But the result is that the task always ends up using the time.
Perfectionism is proportional to deadline pressure. "Good enough" requires a definition of "good." When there's abundant time, "good enough" ratchets upward.
Meetings expand too. A meeting scheduled for an hour takes an hour. The same discussion, if you must resolve it in 30 minutes, usually resolves in 30 minutes.
How to use this for good
Set tighter deadlines intentionally. When you want a decision made, a design drafted, or a prototype built, giving less time forces prioritization. Parkinson's Law is a productivity tool when you use it deliberately.
Time-box rather than scope-box. Instead of "deliver feature X completely," try "spend two weeks on X and ship whatever is done." Time-boxing forces prioritization within the available time.
Use short sprints. Two-week sprints create more focus and delivery rhythm than month-long ones. Shorter cycles mean more frequent accountability and less opportunity for scope drift.
Define done clearly before you start. Without a clear definition of done, work expands into all available time because it's never technically "finished." Clear, minimal acceptance criteria prevent this.
Separate required from optional. Explicitly categorize work into "must have for this to be useful" vs. "nice to have." Required work gets done; nice-to-haves get deferred when time is short.
The flip side: don't over-apply it
Parkinson's Law is not a license to give unrealistically short deadlines. Genuine work has genuine lower bounds. Rushed work produces bugs, debt, and burnout. The goal is to find the right allocation — not the minimum — for the outcomes you need.
The question to ask is not "how can we do this faster?" but "what is the minimum time in which this work can be done well?"
Key questions to surface
- Have we defined "done" clearly enough that we'll know when to stop?
- If we cut the deadline in half, what would we cut from scope? Is that trade-off worth making?
- Are we spending time on things that are genuinely necessary, or things that are comfortable because time permits?
- Is this meeting really a 60-minute meeting, or could it be 30?
- Are our sprint lengths creating focus, or too much room for drift?
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

