القائمة
Track and surface the ratio of ideas captured vs items shipped. Warn when the capture:ship ratio is high — the ideas-rich/finish-poor pattern made visible.
التثبيت باستخدام 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.
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.
| name | nd-velocity-check |
| description | Track and surface the ratio of ideas captured vs items shipped. Warn when the capture:ship ratio is high — the ideas-rich/finish-poor pattern made visible. |
A common neurodivergent productivity pattern: ideas-rich, finish-poor. A session generates 10 new feature ideas, 3 new research threads, and 2 refactoring proposals — and ships zero things. The backlog grows faster than the done list. The backlog feels like progress (it's full of good ideas!) while the actual delivery rate is low.
This is a fluency excess pattern: divergent thinking generates more than convergent thinking can close. Making the ratio visible is the first intervention.
Apply this skill:
Track captures and ships mentally (or read them from a log if available):
Compute the 7-day ratio:
captures in last 7 days : ships in last 7 days
Surface the ratio as a dim, non-blocking note:
"📊 Last 7 days: [N] ideas captured, [M] shipped ([ratio]:1). [Warn/OK]"
Warn when ratio > 5:1 (or when ships = 0 and there are captures):
"📊 Last 7 days: 12 captured, 2 shipped (6:1) — the backlog is growing faster than it's closing. Consider finishing before capturing."
Do not block or moralize. This is a visible metric, not a rule. The user may have a legitimate reason. Surface it once and move on.
On 'finish before capturing': Offer to show the top 3 backlog items (use nd-choicereduce skill).
Metacognition — the ability to observe and regulate one's own thinking — is often reduced in ADHD and related profiles. The capture:ship ratio makes a hidden pattern legible. Once visible, the user can act on it. Without visibility, the pattern continues invisibly.
The fluency excess pattern (high ideation, lower completion) is well-documented in ADHD research and is not a character flaw — it's a cognitive style that benefits from external metrics. "What gets measured gets managed."
The 5:1 threshold is approximate: a healthy ratio in product work is roughly 3:1 (three ideas for every shipped item). At 5:1 and above, the backlog is actively growing in a way that will generate future decision paralysis.
