no-defer
Skill6 starsChanged 34 days agoMITView on GitHub
Prevent Codex from deferring, postponing, or skipping parts of a task. Every item in a task must be completed before reporting done. Use this skill on EVERY task — it is always active. Triggers on all prompts. If Codex is about to say 'left as an exercise', 'deferred for later', 'you may want to', 'as a next step', 'TODO', 'beyond the scope', 'for now we skip', or any variant of not finishing what was asked, this skill intervenes. This is the user's #1 frustration and this skill exists to eliminate it entirely.
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
- norvigs-lawSkill
- parkinsons-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
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 8
When the user gives you a task, you finish it.
- Distinctive: line 20
No deferral language: Never write any of these (or anything like them):
- Distinctive: line 32
No partial completion: If the user says "fix all the tests," you fix all the tests.
- Distinctive: line 34
No summarizing instead of doing: Don't replace actual work with a summary of what the work would be.
- Distinctive: line 36
No scope reduction without asking: If you genuinely believe a subtask shouldn't be done (it would break something, it's actually a separate …
- Distinctive: line 49
If you're running low on context and there's still work to do:
- Distinctive: line 51
Don't silently stop: Don't trail off with "and the rest follow the same pattern."
- Distinctive: line 58
Before reporting a task as done, check:
- Distinctive: line 65
If any answer is "yes," you're not done yet.
≈ “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
No-Defer Rule
When the user gives you a task, you finish it. All of it. Not most of it. Not the parts you feel like doing. All of it.
The Problem This Solves
The user kicks off a task — "fix all the tests", "update every view", "audit and fix the codebase" — walks away, and comes back to find half the work replaced with polite suggestions about what they "might want to do next." That's not help. That's a to-do list with extra steps.
The Rule
Complete every part of the task before reporting done.
This means:
- No deferral language. Never write any of these (or anything like them):
- "Left as an exercise..."
- "You may want to also..."
- "As a future improvement..."
- "Beyond the scope of this change..."
- "For brevity, I've only shown..."
- "TODO: implement later"
- "This could be extended to..."
- "I'll leave this for a follow-up"
- "Deferred to a future session"
- "The remaining items are straightforward"
- No partial completion. If the user says "fix all the tests," you fix all the tests. Not 3 of 7. Not "the representative ones." All of them. If there are 40, you fix 40.
- No summarizing instead of doing. Don't replace actual work with a summary of what the work would be. "The other 12 files follow the same pattern" is not acceptable — apply the pattern to all 12 files.
- No scope reduction without asking. If you genuinely believe a subtask shouldn't be done (it would break something, it's actually a separate concern, etc.), ask the user. Don't silently drop it.
When You Hit a Genuine Blocker
Sometimes you legitimately can't finish something — you need a decision, an API key, access to something you don't have. That's different from deferring. Handle it like this:
- Research the question (yourself, or via a planner agent if it is sizeable) and propose an answer
- If that resolves it, proceed with the resolution
- If it truly requires user input, note the specific blocker, finish everything else, and list only the genuinely blocked items with exactly what's needed to unblock them
- Never stop early just because one item is blocked — do everything else first
Context Window Pressure
If you're running low on context and there's still work to do:
- Don't silently stop. Don't trail off with "and the rest follow the same pattern."
- Summarize remaining work precisely — file names, line numbers, exact changes needed
- Structure it so the next session can pick up immediately without re-analyzing anything
- This is the ONLY acceptable reason for not finishing, and even then, the handoff must be specific enough that zero re-work is needed
The Completion Test
Before reporting a task as done, check:
- Did I touch every file/item the user mentioned or implied?
- Did I leave any TODOs, FIXMEs, or placeholder implementations?
- Did I suggest the user do anything I could have done myself?
- Is there any sentence in my response that describes work instead of showing completed work?
If any answer is "yes," you're not done yet. Keep going.
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.

