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

sequential-opus-orchestrator

Sequential single-Opus backlog walk over the ELAI plan corpus. Triggers when the user says "resume the opus walk", "opus walk", "continue the backlog walk", or "start the opus backlog walk". One paid Opus orchestrates FREE workers (kimi-k2.7 reads, glm-5.2 implements) to drain .elai_cc plans; a deterministic dispatch budget stops the session at a unit boundary and a FRESH Opus resumes from walk-state + handoff. Never two Opus concurrent.

DITlieD · 已有 AI 审核记录

安装与使用

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

npx skills add DITlieD/ELAI-archive --skill sequential-opus-orchestrator

技能说明


name: sequential-opus-orchestrator description: Sequential single-Opus backlog walk over the ELAI plan corpus. Triggers when the user says "resume the opus walk", "opus walk", "continue the backlog walk", or "start the opus backlog walk". One paid Opus orchestrates FREE workers (kimi-k2.7 reads, glm-5.2 implements) to drain .elai_cc plans; a deterministic dispatch budget stops the session at a unit boundary and a FRESH Opus resumes from walk-state + handoff. Never two Opus concurrent.

sequential-opus-orchestrator — the Opus chain controller

Plan of record: workflow/reasoning/TEIKOKU-OPUS-BACKLOG-WALK-PLAN.md (LOCKED D1-D6; do not re-open). State spine: workflow/orchestrator-walk/walk_state.py + walk-state.json (this skill is its production caller). Handoff: workflow/handoff/opus-backlog-walk.md per .Codex/rules/handoff-protocol.md. Binding rules (pointers, not restatements): .Codex/rules/dispatch-core.md (D-1..D-10), .Codex/rules/agent-dispatch-preamble.md (inject on EVERY worker), .Codex/rules/orchestrate-protocol.md (H-1..H-11 bind this controller), .Codex/rules/wiring-enforcement.md (R1-R10), .Codex/rules/production-caller-gate.md (D-030), .Codex/rules/plan-standard.md, .Codex/rules/proof-spine.md (queue order), .Codex/skills/anti-spiral (stagnation), .Codex/rules/commit-cadence.md (overridden ONLY by block 7 below).

HARD INVARIANTS (from the plan's locked decisions)

  • D1 exactly ONE Opus: step 1 of the resume protocol is walk_state.claim_lock(session_id); LockRefused = ABORT immediately with "another Opus holds the walk" — never proceed, never delete the lock by hand.
  • D2 Opus never authors product code and never dictates exact diffs. Blocked executor = escalation ladder (block 4), never "I'll write it myself". Harness tooling (this skill, walk_state.py fixes) is exempt; .elai_cc code is not.
  • D6 all product output lands in .elai_cc/, committed AND pushed per drained plan (block 7). Harness tooling stays local (gitignored), never pushed.
  1. RESUME PROTOCOL (every fresh Opus boot, in order; zero plan-file reads before step 5) 1 claim_lock: python -c "import sys; sys.path.insert(0,'workflow/orchestrator-walk'); import walk_state; walk_state.claim_lock('')" — LockRefused = ABORT (D1). 2 read state: walk-state.json (whole file, it is small) + handoff HEAD only (first ~40 lines: CURRENT STATUS + INDEX). NEVER the handoff body, NEVER plan files, NEVER memory-bank. 3 preflight (all four must pass before any dispatch): a python .Codex/tools/gate_freeze_check.py (a run that can edit its gates writes itself to PASS; also catches the blake3-vs-sha3 env-drift class) b python .Codex/tools/elai_status_query.py --max-age-min 180 (exit 3 = stale: refresh via the feeder before triage) c git -C F:.ELAI_workflow status --porcelain (dirty tree = reconcile first: a half-applied worker edit from a crashed session is DIAGNOSED via reader agents, never reset) d bridge health: curl the lane proxy /v1/models (lane ports in block 3; glm-5-2 AND kimi-k2-7 present, else plan Phase-0 FORK-A/ABORT applies) 4 reconcile cursor: git log + the frozen checkers BEAT walk-state. A DONE row whose commit_sha is not in git log is a LIE: strip it, re-precheck that plan. cursor.pickup names the exact next action; trust it only after this reconcile. 5 continue the per-plan loop (block 2) from cursor; walk_state.record_dispatch() before EVERY worker dispatch; walk_state.heartbeat() at least every stage boundary.

  2. PER-PLAN LOOP (reuses the S-stage prompt layer at .Codex/skills/glm-orchestrate/prompts/ — see its README.md for the evidence chain; substitute evidence_ledger_path=workflow/orchestrator-walk/evidence/{plan_id}.json and plan-status dir=workflow/orchestrator-walk/plan-status/)

  • queue order: PSR-1 precedence (proof-spine.md); take cursor plan first, else queue head.
  • S1 context + S2 integration (paired, kimi) -> S3 precheck-route (NON-SKIPPABLE, prompts/precheck-route.md, wiring agents in mode=precheck): wired=yes -> POLISH route: S9 -> S7 done-gate -> S10 commit. No rebuild. wired=partial|no -> class the work: recognize/activation -> EXECUTE route S4 -> S5 -> S6(+S6b) -> S7 -> S8 -> S9 -> S10. greenfield -> escalation_queue, SET_ASIDE, move on (fail-closed: the 0-commit experiment was blanket-greenfield on the free lane; R2 in the plan).
  • the frozen checkers (production_caller_check.py / python_wire_check.py / wiring_contract_check.py / maintainability_check.py / plan_gate_check.py) run OFF-AGENT, shelled by the controller or the S6 auditor — never self-run-as-authority by the executor (its self-run is a courtesy).
  • S11 memory once per drained PLAN, after S10.
  1. MODEL MAP + DISPATCH PRIMITIVE (explicit D-2 override, cross-family judgment per the D-13 adversary principle)
  • kimi-k2.7 (262k ctx): S1 context-compiler, S2 integration-explorer-elai, spec-grounder reads, S8 hostile review (cross-family: kimi judges glm's work, never glm-audits-glm).
  • glm-5.2 (200k ctx): S5 executor, S6b fixer.
  • deterministic checkers: any lane, off-agent (block 2).
  • the controller: the ONE Opus (this session). Never spawn a second Opus/Fable worker.
  • dispatch primitive: python workflow/glm-orchestrator/glm_dispatch.py (prompt over STDIN, STATUS-line outcome classes incl. INFRA/RATE_LIMITED/CONTENT_POLICY; INFRA never burns an attempt). Lanes a..d -> Windows-side proxy ports 8814/8811/8812/8813 (8810 is permanently untrustworthy Windows-side — a WSL TEIKOKU proxy shadows it; glm-worker.ps1 header has the incident). kimi dispatch = same delegate chain, claudedevin.ps1 -Model kimi-k2-7 on its OWN CLAUDEDEVIN_PORT (never share a live glm lane port). The harness Agent tool CANNOT route glm/kimi (verified 2026-07-06: model unresolvable) — always dispatch via the bridge scripts.
  • every worker prompt starts with the agent-dispatch-preamble pointer line (D-1) + its S-stage template; workers run CLAUDE_COD
阅读完整来源 ↗