Nd functional minimums
Diagnosis-free neurodivergent support skills for AI coding agents, with executive-function scaffolds and always-on Claude/Codex behaviors.
npx -y skills add jpoindexter/nd-skills --skill nd-functional-minimumsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Reduce work to the smallest safe and useful outcome when the user explicitly reports low capacity, depletion, burnout, overwhelm, or asks for the minimum viable version. Preserve safety and function while deferring polish, and execute the reduced outcome when permissions allow.
SKILL.md
1.9 KB, as published. Nobody here has run it
Functional Minimums
Protect function without demanding conventional completeness.
Procedure
- Name the actual outcome in one sentence.
- Separate the work into:
- safety, consent, security, or irreversible-risk controls
- function required for the outcome
- quality that can be deferred
- convention or polish that can be omitted
- Build the smallest version that preserves the first two categories.
- State what was intentionally deferred without framing it as failure.
- Save one obvious re-entry point for later improvement.
Use this compact shape:
Minimum outcome: ...
Do now: ...
Deferred: ...
Done when: ...
Re-entry: ...
Execute Do now when tools and permissions allow. A smaller plan is not the deliverable unless the user asked for a plan.
Decision Rules
- Keep health, safety, data integrity, consent, and reversibility mandatory.
- Let the user define what functional means in their context.
- Prefer reduction over postponement when a useful reduced outcome exists.
- Reduce maintenance cost as well as creation cost.
- Resume from saved state when capacity improves instead of restarting.
Guardrails
Do not use shame as motivation. Do not treat maintenance, productivity, tidiness, or polish as moral worth. Do not silently narrow legal, medical, financial, security, or other high-stakes requirements.
Source Basis
Primarily synthesize KC Davis's function-first and morally neutral care-task approach, with support-level matching from Kolberg and Nadeau and burnout-aware pacing from Megan Anna Neff. Generalize the method to knowledge work and software tasks.