diverge
Skill7 starsChanged 21 days agoMITView on GitHub
Structured divergence engine for consequential, open-ended decisions. Generates a wide, deliberately non-anchored option space by spawning isolated parallel sub-agents under different cognitive frames, then runs a separate critic pass that scores, declusters, and deepens the best. The divergent complement to /deep-analysis. Warranted only when a decision is both hard to reverse or wide in blast radius AND genuinely open with several structurally different answers — architecture and platform strategy, design-space exploration, de-anchoring a premature conclusion, or a high-stakes what are our options. Triggers include diverge, brainstorm options, explore alternatives, option space, divergent thinking. Because it fans out many agents in parallel it is not for cheap or adjacent asks — naming, wording, picking between two known libraries, or any question with one defensible answer should be answered directly.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- AsimSayed/claude-skillstheir own version, first seen Oct 13, 2026
- Kshitijpalsinghtomar/depth-skillstheir own version, first seen Oct 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Kshitijpalsinghtomar/depth-skills★ 5same name
- AsimSayed/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- api-contract-testingSkill
- browser-testingSkill
- ci-cd-templatesSkill
- code-review-checklistSkill
- context-escalationSkill
- deep-analysisSkill
- deep-readSkill
- deliverySkill
- deployment-runbookSkill
- docker-deploymentSkill
- executeSkill
- experiment-loopSkill
- git-workflowSkill
- handoffSkill
- infrastructure-as-codeSkill
- investigateSkill
- kubernetes-opsSkill
- library-docsSkill
- multi-agent-orchestrationSkill
- observability-stackSkill
- remote-triggersSkill
- repo-contextSkill
- scheduled-tasksSkill
- security-scanSkill
- skill-creatorSkill
- sre-runbooksSkill
- ui-guidelinesSkill
- verified-handoffSkill
- worktree-workflowSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
Isolation invariant: No generator receives another's output.
- Distinctive: line 52
Gate: All frame agents returned.
- Distinctive: line 56
Only now is judgment allowed.
- Distinctive: line 65
Gate: Every approach scored; traps flagged with reasons.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Diverge — Divergent Option-Generation Engine
Break premature convergence. Autoregressive reasoning commits to the first plausible answer; this skill manufactures genuine breadth before any evaluation, then converges deliberately.
Core principle: Separate generation from judgment. Ideas are generated in ISOLATION (no branch sees another, so none can anchor on another), and only a SEPARATE critic pass is allowed to evaluate. Evaluating while generating is the failure mode this skill exists to prevent.
Pre-Flight Gate
Activation is decided by the frontmatter description alone — this file is read only AFTER the skill has been selected. Nothing here can prevent over-triggering, so this gate is a post-selection redirect, not a filter.
Before proceeding, check the ABORT conditions below. If any holds, STOP, say in one line which one
fired, and take the redirect instead of fanning out any agents. Being invoked — including a literal
/diverge, "brainstorm options", "explore alternatives", or "give me alternatives" — does NOT
override an ABORT: the phrasing that selected this skill is not evidence the problem is open.
| ABORT when the ask is… | Redirect |
| Syntax, a definition, a factual lookup, arithmetic, a deterministic transform | Answer directly |
| A bug with a single known root cause | /investigate |
| A decision the user has already made | /execute — just build it |
| Following an explicit step-by-step instruction | Do the steps |
| Low-stakes or adjacent — naming, wording, two known libraries | Answer directly with the inline obvious/alternative/trap (anti-anchoring rule) |
| Consequential but CLOSED — one approach is clearly right | State it, plus a one-line trap check |
| Open but cheaply reversible — trying one costs less than exploring | Pick the obvious one and try it |
PROCEED only when no ABORT fired AND consequence × openness both hold — hard to reverse, wide blast radius, or high cost of being wrong, AND several viable, structurally different approaches plausibly exist. The gate is consequence × openness, NOT token cost.
Phase 1: DIVERGE — Isolated Parallel Generation
- Restate the problem in one sentence and list the hard constraints (these go to every frame).
- Pick ~5 frames from the table below whose vantage best surfaces structurally different approaches for THIS problem. Use 4 for narrow problems, up to 6–7 for wide ones. More than 7 hits diminishing returns (see
multi-agent-orchestration). - Send a single message with multiple
Agenttool calls for parallel agent launches — one Agent per frame, all in the same message. Each runs in isolation and never sees the others. - Give every sub-agent the SAME generator-only instruction:
You are a GENERATOR working under the "
<FRAME>" frame. From this vantage only: PROBLEM:<one-sentence problem>CONSTRAINTS:<hard constraints>Produce 3–5 genuinely distinct approaches. For each: a one-line name, the core idea (2–3 sentences), and the single biggest risk. RULES: Do NOT evaluate, rank, hedge, or pick a winner. Do NOT mention other frames or approaches (you cannot see them). Favor range over safety — at least one approach must be non-obvious. Output a flat list. No preamble.
Isolation invariant: No generator receives another's output. No generator is asked to compare, score, or choose. Violating this re-introduces the anchoring the skill exists to remove.
Gate: All frame agents returned. You hold a flat, unscored, un-deduplicated pool. No evaluation has happened yet.
Phase 2: FOCUS — Separate Critic Pass
Only now is judgment allowed. Do this yourself (or one critic agent) over the WHOLE pool.
- Score each approach 1–5 on three axes, then weighted total:
score = 0.25·novelty + 0.45·viability + 0.30·fit(novelty = distance from the obvious default; viability = buildable under constraints; fit = serves the real goal) - Flag traps — high-novelty/seductive approaches that fail a hard constraint. List each with the SPECIFIC constraint it violates. Traps are reported, never silently dropped.
- Cluster survivors by underlying angle (collapse near-duplicates from different frames; note where isolated frames converged — that convergence is signal).
- Deepen the top 3 by weighted score: mechanism, key trade-off, first failure it would hit, rough cost/effort.
Gate: Every approach scored; traps flagged with reasons; clusters formed; top 3 deepened.
Output Shape
- Brief — one line: the problem and the constraints that bind it.
- Wide set — full pool as a flat list, each with a chip
[N x.x | V x.x | F x.x → total]. - Converge — shortlist — top 3, with the single best non-obvious pick STARRED (★) and one line on why it beats the obvious default. List traps separately below, each with the constraint it violates.
- Deepened branches — the mechanism/trade-off/first-failure/cost for the top 3.
- One provocation — a single closing line: the assumption most worth challenging, or the next option if constraints loosened. Exactly one.
Anti-Patterns
| Bad Habit | What /diverge Does Instead |
| Commit to the first plausible answer | Forces a wide isolated pool before any judgment |
| Generators that rank or hedge themselves | Generator-only instruction; judgment is a separate pass |
| Branches seeing each other's ideas | Isolation invariant — parallel Task calls, no shared context |
| Running on closed/low-stakes problems | Pre-flight gate aborts unless consequence AND openness hold |
| Dropping the seductive-but-wrong option silently | Traps flagged with the exact constraint violated |
| Ending with a menu of equals | One starred non-obvious pick + one provocation |
| 12 frames "to be thorough" | ~5 frames; diminishing returns past 7 |
Integration with Other Skills
/diverge is the divergent complement to the convergent /deep-analysis.
| Situation | Use |
| Open-ended, consequential — "what are our options?" | /diverge (this skill) |
| One approach chosen — pressure-test it | /deep-analysis |
| Bug with unknown root cause | /investigate |
| Winners chosen — build them | /execute |
| Cheap inline judgment call | anti-anchoring rule habit — no skill needed |
Hand-off chain: /diverge (widen) → pick winners → /deep-analysis (validate) → /execute (build). Never feed the raw wide set to /execute; converge first.
Cost Note
The Diverge phase spends ~5 parallel sub-agents plus one critic pass — real but bounded. Justified ONLY by the pre-flight gate (consequence × openness), never by default. On a closed or low-stakes problem this skill is WRONG, not merely expensive: it manufactures noise and false choices.
Frames Table
| Frame | Vantage prompt |
| Regulator | "What does compliance, audit, security, least-privilege demand? Design for the reviewer and the breach." |
| Attacker | "How would I break, abuse, or exploit this? Design the approach that survives an adversary." |
| Inversion | "What guarantees failure? Now invert each failure into a design constraint." |
| First-principles | "Ignore prior art. From the raw requirement and cost/physics, what is the minimal thing that works?" |
| Markets / incentives | "Who pays, who benefits, what behavior does this reward? Follow the incentives and the cost curve." |
| Biology / evolution | "Treat it as an organism: how does it adapt, self-heal, degrade gracefully, scale without central control?" |
| Operator / 3am | "I am on-call when this breaks. What is observable, reversible, boring to run? Optimize for the worst night." |
| Scale-10x | "Requirements hold but load/data/team are 10x. Which approaches survive, which shatter?" |
| Constraint-removal | "Which 'hard' constraint is actually assumed? Remove the most load-bearing one — what opens up?" |
| Future-maintainer | "Someone inherits this in two years with no context. What is simplest to understand, change, and delete?" |
References
anti-anchoringrule — the always-on inline habit this skill is the heavy mode fordeep-analysisskill — the convergent partner; validates the chosen winnermulti-agent-orchestrationskill — parallel-launch idiom; 5–7-agent diminishing-returns limitexecuteskill — builds the converged winners
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

