omnilane 0.21.0 → 0.31.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +2 -2
- package/.claude-plugin/plugin.json +1 -1
- package/CHANGELOG.md +26 -1
- package/README.ja.md +27 -0
- package/README.ko.md +27 -0
- package/README.md +29 -0
- package/README.zh-CN.md +27 -0
- package/README.zh-TW.md +27 -0
- package/VERSION +1 -1
- package/bin/omnilane +8 -3
- package/hooks/routing-instruction.md +16 -7
- package/package.json +1 -1
- package/plugin.json +1 -1
- package/scripts/doctor.sh +26 -0
- package/scripts/lib/goal-loop.sh +572 -678
- package/skills/omnilane/SKILL.md +9 -4
package/skills/omnilane/SKILL.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: omnilane
|
|
3
|
-
description: 'Universal model-routing table + cross-vendor dispatch for ANY harness (Claude Code, Codex, Grok Build, Antigravity). Use when delegating subtasks, choosing a model for work, planning multi-part tasks, or when asked about model routing, delegate, dispatch, which model, tier selection, escalate, 派工, 模型路由. One routing table;
|
|
3
|
+
description: 'Universal model-routing table + cross-vendor dispatch for ANY harness (Claude Code, Codex, Grok Build, Antigravity). Use when delegating subtasks, choosing a model for work, planning multi-part tasks, or when asked about model routing, delegate, dispatch, which model, tier selection, escalate, 派工, 模型路由. One routing table; implementation work dispatches by default via dispatch.sh — the main loop self-executes only reserved commander items.'
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# omnilane — one routing table, every harness
|
|
@@ -9,7 +9,11 @@ You (the main loop) may be Claude, GPT, Grok, or Gemini. The procedure is identi
|
|
|
9
9
|
|
|
10
10
|
1. **Identify your main model.** You know which model you are running as.
|
|
11
11
|
2. **Split the work into subtasks and classify each into a lane** (table below).
|
|
12
|
-
3. **
|
|
12
|
+
3. **Dispatch implementation work by default — even when the lane's model is
|
|
13
|
+
you.** Self-execute only reserved commander items: planning and
|
|
14
|
+
decomposition, writing task briefs, reviewing reports, acceptance checks,
|
|
15
|
+
replies to the operator, git commit/push, read-only verification, and
|
|
16
|
+
fixes of one line or less. Dispatch:
|
|
13
17
|
`<repo>/scripts/dispatch.sh [--vendor V] [--mode work] [--workdir DIR] <lane> "<task>"`
|
|
14
18
|
Add `--background` for long tasks; poll with `scripts/jobs.sh status|result <id>`.
|
|
15
19
|
Before changing lane order from anecdotal outcomes, run
|
|
@@ -155,8 +159,9 @@ dispatch stay in this skill and the CLI. Manage the local board with
|
|
|
155
159
|
|
|
156
160
|
## Per-model notes (apply the row matching YOUR main model)
|
|
157
161
|
|
|
158
|
-
- **Claude (Fable/Opus main)**: top judgment and taste are yours
|
|
159
|
-
|
|
162
|
+
- **Claude (Fable/Opus main)**: top judgment and taste are yours, but
|
|
163
|
+
implementation still dispatches by default — self-execute only reserved
|
|
164
|
+
commander items; push all coding volume out to the lanes.
|
|
160
165
|
- **Claude Sonnet main**: coordination/tools/mid-tier coding only; never
|
|
161
166
|
self-assign top judgment or hardest implementation.
|
|
162
167
|
- **GPT Sol main**: hardest coding + hard judgment are yours (use max for
|