القائمة
Detect complex or multi-step requests and suggest structured planning before acting. Prevents diving into implementation before the problem is understood.
التثبيت باستخدام 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.
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.
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-complexity-gate |
| description | Detect complex or multi-step requests and suggest structured planning before acting. Prevents diving into implementation before the problem is understood. |
Planning and organization difficulty: for many neurodivergent developers, complex multi-part tasks can trigger one of two failure modes — paralysis (not knowing where to start) or premature execution (jumping to implementation before understanding the full scope, then having to restart).
Both are costly. The complexity gate catches requests that warrant a plan before any tool call.
Apply this skill when a user request contains two or more of the following signals:
Scope signals:
Ambiguity signals:
Compound-task signals:
Score the request. Silently assess: how many complexity signals are present?
At 2+ signals and plan mode not active: Before any tool call, emit a one-line note:
"⚠ This looks complex ([N] signals). Consider planning the approach before executing —
/planmodeon, or I can outline steps first?"
If the user already said "just do it," "use your judgment," "do not ask," or supplied a terminal condition, do not turn this note into a question. State that you are structuring the work internally and proceed.
If the user says 'outline steps': Produce a numbered execution plan with:
Use $nd-task-decomposition when dependencies are hidden or the user needs an executable Now/Next/Later surface rather than a high-level plan.
Never block. If the user says "just do it", proceed immediately. The suggestion is a cognitive scaffold, not a gate.
When plan mode IS active: Skip the suggestion — the user already chose structured execution.
Planning and organization are direct executive function components. For people with EF challenges, the blank-page problem is often most acute at the START of a complex task. A brief plan — even if modified — provides the scaffolding that makes initiation possible. The alternative (diving in without a plan) often leads to scope drift, rework, and the "I'll just start over" loop.
Environmental manipulation principle: structure the task environment so it's easier to start correctly than to restart.
