القائمة
Before starting a new task thread, surface any tasks that are more than halfway complete. Ask whether to close one first. One-tap dismiss. Never blocks.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Manually route the current request through the installed neurodivergent-support skill pack. Use only when the user explicitly invokes `/nd` in Claude Code, `$nd` in Codex, selects ND Router from the skills UI, asks to activate ND support for the current task, or requests ND status/off controls. Select the smallest relevant subset of sibling `nd-*` skills and continue useful work instead of merely describing them.
When presenting options or a backlog, show only the top 3. Hidden items are noted but not shown until one choice is completed.
Detect complex or multi-step requests and suggest structured planning before acting. Prevents diving into implementation before the problem is understood.
Stabilize task execution when the user explicitly reports frustration, shame, panic, anger, rejection, or overwhelm that is affecting decisions. Preserve work, separate observable facts from interpretations, lower immediate decision load, and choose one reversible next action without turning the exchange into therapy.
Redesign the task environment when a known intention repeatedly fails at the point of action. Use when reminders arrive too early or late, tools or state are hard to find, choices or steps create friction, a system depends on memory, or repeated failure shows that effort alone is not enough.
Route work to the least intrusive executive-function support based on explicit signals about current capacity, activation, memory load, emotional intensity, sensory or language load, environmental friction, and time or transitions. Use when a task feels stuck, overwhelming, difficult to hold in mind, or when the user asks for neurodivergent-friendly support without wanting an intake or coaching ritual.
| name | nd-closuregate |
| description | Before starting a new task thread, surface any tasks that are more than halfway complete. Ask whether to close one first. One-tap dismiss. Never blocks. |
Task-switching and closure: many neurodivergent developers find it easy to start new things and hard to finish them. This is partly because starting is novel (dopamine) and finishing is often repetitive (cleanup, docs, edge cases). The result: a session full of half-finished tasks that each need context reload to resume.
The closure gate is a gentle check before starting a new major thread: "there are 2 things almost done — want to close one first?"
Apply when:
Trigger signals:
git status or equivalent would show uncommitted changes from an unfinished subtaskCheck for open items. Before engaging with the new task, review:
If 1 or more items are > 50% complete: Surface exactly one question:
"Quick check: [Item A] and [Item B] look close to done from this session. Want to close one before switching?"
Offer exactly 3 options:
On 'skip': Proceed immediately. No second question.
On 'yes': Return to the in-progress item. Provide a one-sentence re-orient:
"Back to [item]: [what was done], [what remains]. This should take [honest time estimate]."
On 'show me what's open': List the in-progress items with completion estimates.
Task completion is a dopamine-dependent reward. For people with ADHD, the dopamine signal at task completion is often weaker or delayed compared to the dopamine signal at task start. This asymmetry makes finishing feel less compelling than starting.
External accountability structures (making the open items visible, asking the explicit question) substitute for the missing internal completion signal. Research shows that visible progress and explicit closure moments meaningfully increase task completion rates in ADHD populations.
One-question format is deliberate: asking multiple questions about open items recreates the overwhelm they're designed to address. One specific item, one yes/no question.