跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

adhd

Divergent ideation across model families — the same brainstorm, but each cognitive frame is handed to a different model (Claude sub-agent, OpenAI Codex, a cheap third via OpenCode) so the ideas diverge by frame and by model priors at once. Use for open design questions, architecture and API shape, naming, schema choices, fuzzy bugs with no known root cause, or on "multi adhd", "brainstorm with everyone", "wide ideas from all models". Skip for lookups, syntax, and anything phrased as "quick", "standard" or "canonical".

szarkans · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add szarkans/multi --skill adhd

技能说明


name: adhd description: >- Divergent ideation across model families — the same brainstorm, but each cognitive frame is handed to a different model (Claude sub-agent, OpenAI Codex, a cheap third via OpenCode) so the ideas diverge by frame and by model priors at once. Use for open design questions, architecture and API shape, naming, schema choices, fuzzy bugs with no known root cause, or on "multi adhd", "brainstorm with everyone", "wide ideas from all models". Skip for lookups, syntax, and anything phrased as "quick", "standard" or "canonical". allowed-tools: Bash, Read, Grep, Glob, Agent argument-hint: "[the problem to think wide about]" metadata: based-on: "ADHD by UditAkhourii — https://github.com/UditAkhourii/adhd (MIT)"

Wide ideas, several models

!"${CLAUDE_SKILL_DIR}/../../scripts/probe.sh"

The first three answers a model gives are the answers a senior engineer gives in thirty seconds. Correct, forgettable. The interesting ones live past number three. Cognitive frames push one model out there; different model families start from different priors and land somewhere else again. This skill uses both axes at once and pays for one.

$SCRIPTS is whatever the probe printed as scripts-dir:.

On any host other than Claude Code the line above is plain text, nothing ran. Your first step is then to run the probe yourself and read its output as if it were printed here: <dir of this SKILL.md>/../../scripts/probe.sh — the plugin's scripts/probe.sh, two directories above the real file (resolve symlinks first: realpath of this SKILL.md, then ../../scripts/probe.sh).

If the line above reads Shell substitution failed instead of probe output, the session is in a git worktree whose shell gate refused the header; the plugin is fine. Run "${CLAUDE_SKILL_DIR}/../../scripts/probe.sh" yourself, as one plain command with nothing but the path, and read scripts-dir: from that.

Pre-flight

If the user typed /multi:adhd or asked for it by name, go. They opted in.

Otherwise abort and answer directly unless all three hold: the question has several viable answers, the obvious answer being wrong is expensive, and the user did not say "quick", "just", "standard", "canonical" or "one-line".

Phase 1 — diverge (no critic)

Pick 5 frames from the table. Bias to code/design tags for code-shaped problems, always keep one wild for range. Vary the picks between runs so the same problem gives a different pool the second time.

Hand each frame to a different backend, rotating. With all three alive:

framebackend
1host sub-agent (the model running this skill)
2Codex
3OpenCode
4host sub-agent
5Codex

Start the external models first — they take 30–90 seconds and OpenCode spends most of a minute waking up. Launch the host-side frames while they run.

RUN="$($SCRIPTS/run-dir.sh --slug <two-to-four words: the project and the job, e.g. skills-fixing-multi>)"

$SCRIPTS/ask.sh --question-file "$RUN/adhd-f2.md" --out-prefix "$RUN/adhd-f2" \
                --backend codex --effort medium &
$SCRIPTS/ask.sh --question-file "$RUN/adhd-f3.md" --out-prefix "$RUN/adhd-f3" \
                --backend opencode &
wait

On a host whose shell tool caps a call and kills the process group at the cap (OpenCode: two minutes by default), drop the & and the wait: add --detach to each ask.sh call (with > "$RUN/adhd-fN.log" 2>&1), return, and collect with $SCRIPTS/wait.sh --prefix "$RUN/adhd-fN" --max 100, called again while it exits 1.

$RUN is this session's own directory, so two sessions brainstorming at once do not overwrite each other. Shell variables do not survive between commands — repeat that first line in every later block that uses $RUN, including the frame files you write above.

One frame per file, one file per run. --backend exists precisely so the two CLIs can get different questions in parallel instead of the same one.

Every branch — agent or CLI — gets only the problem, the user's context, its own frame, and this instruction:

You are in DIVERGENT mode. You are a generator, not a critic. Generate 6 short distinct ideas under this frame. Each idea is one phrase or one sentence. Do not evaluate. Do not rank. Do not hedge. The first three obvious answers everyone would give are banned. Push past them into the awkward middle. Output a JSON array only. No prose before or after. [{"text": "...", "rationale": "..."}, ...]

For the CLIs add one line: "Do not read files or explore the repository" unless the problem is genuinely about this codebase. Otherwise OpenCode spends its run doing ls and git status before it starts thinking.

Isolation is the whole method. No branch sees another branch's output. Do not feed one frame's ideas into the next prompt, and do not write the branches out sequentially in your own context to save calls — that is one wider thought wearing five hats, not five branches.

When a backend is missing or dies

The probe says who is alive. A missing backend's frames go to host sub-agents, and the report says so in one line: "Codex not installed — frames 2 and 5 ran as host agents." A host with no sub-agents at all does not run frames inline — sequential frames in one context see each other's ideas, which is the one thing this method forbids. Give those frames to the external backends instead (a second ask.sh call per frame, different backend each), or run fewer frames and say so. Never quietly re-label a host-model idea as Codex's. Read the one-line text in ${RUN}/...-codex.txt.dead and ${RUN}/...-opencode.txt.dead for codex: ... / opencode: ... reasons; those files explain missing/failed backends. codex: MISSING, opencode: NO OUTPUT, opencode: TIMEOUT and an empty file are all "did not run" — check the file content, not just that a file exists. Mention /multi:setup in the report when a backend is missin

阅读完整来源 ↗