AGENT SKILL

gilgamesh-esl-hop

ESL lifecycle hop — in an ESL-enabled project (tonberry MCP available), when a fallthrough mission is authored as an ESL change, Gilgamesh is the MAKER and drives proposed→in_progress→(ready-for-verify). Gilgamesh NEVER self-verifies — maker≠checker is mechanically enforced (C4), so a distinct checker owns the verified transition. Absent tonberry → run the normal GILGAMESH cycle (ESL opt-in); never hard-fail.

License 许可
Apache-2.0
所属仓库
Rynaro/magicite
最近更新
2026-10-14
Stars
★ 2
Forks
0

01 前言 Front Matter

name
gilgamesh-esl-hop
metadata
{ "phase": "cross-cutting", "methodology": "Gilgamesh" }
description
ESL lifecycle hop — in an ESL-enabled project (tonberry MCP available), when a fallthrough mission is authored as an ESL change, Gilgamesh is the MAKER and drives proposed→in_progress→(ready-for-verify). Gilgamesh NEVER self-verifies — maker≠checker is mechanically enforced (C4), so a distinct checker owns the verified transition. Absent tonberry → run the normal GILGAMESH cycle (ESL opt-in); never hard-fail.

03 SKILL.md 正文

ESL Lifecycle Hop — Gilgamesh (the MAKER)

When to use

Load this skill in an ESL-enabled project (mcp__tonberry__* tools available) when a fallthrough mission is carried as an ESL change with acceptance_checks. Gilgamesh is the MAKER — it authors the change and drives it to the point of verification, then hands the verify to a distinct checker. maker ≠ checker is mechanically enforced (tonberry verify check C4). For the full lifecycle and role bindings, see the nexus cortex methodology/cortex/esl-protocol.md.

Your hop

You make this change; you do not check it. The Excalipoor rule and maker≠checker point the same way: your own signal never certifies your own work.

  1. right-size + propose — the mission enters ESL as a change. Run the normal GILGAMESH cycle (Gauge → Inventory → Lock → Grind) to author it, applying mutations sandbox-first and gating each on its NAMED external oracle (skills/grind/SKILL.md).
  2. drive the maker transitions — mcp__tonberry__transition --change_id <id> --to_status in_progress, then complete the work; leave the change ready-for-verify. Set change.json.maker = gilgamesh.
  3. compose the maker artefact — your result PROPOSE (skills/attest/SKILL.md), from.eidolon = gilgamesh. This value populates change.json.maker.
  4. hand the verify to a checker — you MUST NOT call mcp__tonberry__transition --to_status verified yourself. The checker's verify envelope MUST carry from.eidolon != gilgamesh (else C4 fails by construction). Emit the change as ready-for-verify; the orchestrator routes the checker.
  5. on a returned failing check → treat it as Grind feedback: re-enter the loop under recover/escalate and fix it as the maker. You never flip your own change green.

Invariants

  • Maker, not checker. change.json.maker = gilgamesh. Gilgamesh never composes the verified transition or the verify envelope — a distinct checker does. Self-verifying would be exactly the maker≠checker violation the gate exists to stop, and exactly the Excalipoor self-attestation the methodology forbids.
  • External-only verify still holds. Even as maker, every mutation is gated by a NAMED external oracle before you call the change ready — never self-critique.
  • Worker, never router. You do not dispatch the checker; you emit the change ready-for-verify and the orchestrator routes it (handoffs.downstream: []). If the change needs a specialist sub-mission, emit a handoff-request (skills/attest/SKILL.md).
  • Graceful skip / fail-open — if mcp__tonberry__* tools are unavailable, run the normal GILGAMESH cycle and never hard-fail. ESL is opt-in; Gilgamesh is EIIS-standalone-conformant and works without tonberry.

ESL Lifecycle Hop — Gilgamesh (the MAKER, maker≠checker mechanically enforced, never self-verifies)

04 同仓库更多 Skills

Rynaro
Rynaro/magicite

wine-dxvk-cache-clear

Clear a stale DXVK shader cache that is causing graphical corruption in a Wine or Proton game. Use when: a game shows corrupted textures or shader flicker that started after a driver or DXVK version change.

★ 2
Rynaro
Rynaro/magicite

steam-download-region-fix

Fix a Steam client stuck at very low download speed by changing its download region. Use when: Steam downloads are far below the local internet speed for every game, not just one.

★ 2
Rynaro
Rynaro/magicite

proton-battleye-eac-toggle

Toggle BattlEye or Easy Anti-Cheat runtime support for a Steam Proton game. Use when: a multiplayer game refuses to launch with an anti-cheat error under Proton.

★ 2
Rynaro
Rynaro/magicite

vivi-verify-incoming

Load when reading any upstream artefact handed off to Vivi that carries a sibling .envelope.json. BLOCKING per ECL §6.2.2: the orchestrator MUST have verified the envelope's SHA-256 (eidolons verify-envelope --block / eidolons run --verify) and recorded a verify_pass before dispatch. If no verify_pass exists for the message_id, or a verify_fail is present, REFUSE to process the payload and hand back to the orchestrator. Symmetric receiver gate — every Eidolon enforces it identically.

★ 2
Rynaro
Rynaro/magicite

vivi-parallel-tracks

Load ONLY under TRANCE authorization when the Plan phase yields N independent, non-overlapping implementation tracks (disjoint file sets). Operationalizes the TRANCE G4 form — parallel multi-track implementation in mandatory git-worktree isolation, max 5 clean-context tracks, a per-track verifier cascade, a non-fungible per-track ≤3 reflection budget, explicit stop conditions, and a single-threaded merge/aggregation step. Absent TRANCE gating, Vivi runs exactly as today: single-track A→P→I→V→Δ/R.

★ 2
Rynaro
Rynaro/magicite

vivi-methodology

Full Vivi cycle reference — A(nalyze) → P(lan) → I(mplement) → V(erify) → Δ(Delta)/R(eflect). Use when the task is a non-trivial feature implementation in a brownfield codebase and you need the complete methodology reference: complexity routing, evidence-grounded planning rules, test-anchoring requirements, and failure-escalation thresholds.

★ 2