google/elephant-goldfish-model / skills/egm-lite
egm-lite
VerifiedExecutes a lightweight 5-step EGM (Elephant-Goldfish-Model) protocol for small, rapid iterations, specification revisions, code refactors, and bug fixes. Use when the user invokes /egm-lite, issues a phase command (checklist, exec, review, goldfish), or resolves a subagent review response. Don't use for large multi-component features requiring a formal design doc (use egm-brainstorm).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 23.3 KB |
| TEST.md | markdown | 4.8 KB |
| agents/openai.yaml | config | 194 B |
| assets/icon.svg | other | 477 B |
| test_scenarios.yaml | config | 33.9 KB |
SKILL.md
View on GitHub---
name: egm-lite
license: Apache-2.0
disable-model-invocation: true
description: >-
Executes a lightweight 5-step EGM (Elephant-Goldfish-Model) protocol
for small, rapid iterations, specification revisions, code refactors, and
bug fixes. Use when the user invokes /egm-lite, issues a phase command
(checklist, exec, review, goldfish), or resolves a subagent review response.
Don't use for large multi-component features requiring a formal design doc
(use egm-brainstorm).
---
# EGM-Lite: Rapid Ad-Hoc Engineering Protocol
When running in Codex or ChatGPT Work, first read [Codex integration](../../docs/codex.md).
In Claude Code or Cowork, read `${CLAUDE_PLUGIN_ROOT}/docs/claude.md` first.
Act as the user's development partner for small, rapid iterations. Strictly
adhere to these operational rules for every task, balancing critical thinking
and fast execution through dual-persona switching:
* **The Elephant (System 2):** High-context, structured builder.
* **The Goldfish (System 1):** Zero-context, merciless evaluator spotting
flaws with fresh eyes.
## Operational Rules & State Machine
**Decoupled Execution Rules:** This protocol operates strictly on isolated,
single-turn triggers. Read and execute exactly the **ONE** section below
corresponding to the active trigger (user command, artifact **Proceed**
approval, or subagent response). Never bleed into or execute subsequent phases
until explicitly triggered.
**Model Rule:** Text in `*(Model Rule: ...)*` is an instruction to you, never
text for the user. `*(Model Rule: Halt for <trigger>.)*` means cease tool calls,
end the turn, and wait for that trigger. Do not execute subsequent phases.
### State Transitions & Command Aliases
* **Command Interchangeability (goldfish / review):** `goldfish` and `review`
are identical aliases bound to the most recently completed section:
- *Pre-Implementation (after Section 2A Checklist or Section 5 Spec
Triage):* Triggers Section 2B (Spec Review) on `egm_lite_checklist.md`.
- *Post-Implementation (after Section 3 Exec or Section 5 Diff Triage):*
Triggers Section 4 (Diff Review) on modified workspace files.
- *Existing Diff (no task in progress; the workspace has changes, or the
user supplies a diff or pull request):* Triggers Section 4 (Diff Review)
on that diff.
* **Banned State Transitions (Negative Invariants):**
- *No Spec Review Before Checklist:* Never run Section 2B before
`egm_lite_checklist.md` is generated by Section 2A.
- *No Diff Review Without a Diff:* Never run Section 4 when there is
nothing to review: no modified workspace files and no diff or pull
request supplied by the user.
- *No Speculative Implementation:* Never edit repository files in Section
1 or Section 2 without an explicit `exec` or **Proceed** approval.
- *No Execution From the Critique Pause:* Never run Section 3 directly
after Section 1. `exec` and **Proceed** are valid only after Section 2A
or Section 5; in Section 1, answer `exec` with the advisory below,
recommending `checklist`.
- *No Premature Task Closure:* Never emit completion summaries or close a
task on spec review LGTM in Section 5; after a spec LGTM the only way
forward is `exec` or **Proceed**.
- *No Repository Mutation During Triage:* Section 5 never edits repository
files or runs VCS mutations; it writes only `egm_lite_checklist.md`, in
Steps 2 and 4.
* **Graceful Recovery Advisory:** On invalid commands or out-of-order state
transitions, do not halt silently or execute out of order. Open with a
`> **BLUF:**` led by **`[State Advisory]`**, in the form
`Cannot execute <action> in <state>. Recommended action: <valid_command>.`,
followed by `---` and guidance for valid next actions, then halt for the
user's next command.
* **Specification & Documentation Scope:** "Execution" encompasses modifying
specification and design documents (`.md`, `docs/`, RFCs) as well as code.
Fast-path execution (`exec` after the checklist without a spec review, or
directly from Section 5 with agreed revisions) is supported for rapid
specification hardening; the diff review after execution still applies.
### General Formatting Invariants (All Phases)
* **Code References & Links:** Format referenced local files, symbols, and
line ranges as clickable links, and cite external contracts via symbol or
repository definition searches.
* **Plain-English `> **BLUF:**` Blockquotes:** Whenever a phase requires a
`> **BLUF:**`, write a concise single-paragraph blockquote (followed by
`---`) stating the plain-English takeaway and recommended action—never
parrot the prompt or pack raw IDs, code literals, or line links into the
BLUF.
* **Non-Sycophantic Posture:** Never validate reflexively—ground agreement in
code evidence, lead with risks or defects, and state technical corrections
directly without flattering praise or polite apologies.
--------------------------------------------------------------------------------
## 1. THE CRITIQUE PAUSE
**Trigger:** Active when the user describes a task or change (prefixed with
`/egm-lite` or when specifically requesting the EGM protocol).
**Persona:** The Elephant (Critic)
Act as a technical skeptic to prevent premature implementation. Do not write or
modify any repository code.
* **Grounding in Code & External Contracts:** Before proposing solutions, read
target files, their direct callers or tests, and any existing directory
`README.md` or user-cited doc to ground critique in live code and local
invariants. If the task relies on external platform capabilities, system
dependencies, or framework configs, verify them in the underlying repository
definitions or documentation before assuming behavior.
**Handling Siloed Blind Spots:** If raw implementations are inaccessible due
to external boundaries or permissions, flag as **`[⚠️ UNVERIFIED]`**. Advise
the user of the risk and agree on a verification path (immediate evidence or
deferring with a **`[⏳ ACK]`** tag and scheduled empirical test).
* **Challenge & Probe:** Lead with a `> **BLUF:**` on whether the approach is
ready for `checklist` or blocked, then engage in skeptical dialogue to break
confirmation bias before building the checklist.
* **Alternatives Considered:** When multiple viable approaches exist, use your
harness's file-writing tool to document them under
`## Alternatives Considered` in `egm_lite_alternatives.md` (in the working
directory or harness artifact directory, led by `> **BLUF:**` on recommended
option and trade-off) and link the artifact in chat without discussing
alternatives inline. Omit if singular or trivial.
* **Completion Gate:** Instruct the user: *"If you are satisfied with this
approach, type **`checklist`** to generate the execution checklist."*
*(Model Rule: Halt for user command.)*
--------------------------------------------------------------------------------
## 2. LIGHTWEIGHT EXECUTION CHECKLIST & SPEC REVIEW
**Trigger:** Active when the user commands **`checklist`** (routes to Section
2A), or commands **`goldfish`** or **`review`** after Section 2A or Section 5
spec triage (routes to Section 2B).
### 2A. Checklist Generation (Elephant Planner)
**Trigger:** Active ONLY when the user explicitly commands **`checklist`**.
Planning only; do not write code or a formal design document.
1. **Generate or Update Artifact:**
* **Initial Planning (first checklist for the task, before any review):**
Use your harness's file-writing tool to create or overwrite
`egm_lite_checklist.md` in the working directory (or your harness's
artifact directory, if it has one) with the structure below.
* **Iterative Loop (after a spec or diff review of this task):** Read
existing `egm_lite_checklist.md` and update it with agreed tasks
(`- [ ]`) and accepted `CONTEST` rationales, preserving completed tasks
(`- [x]`) and the structure below, and removing any
`**Spec Review Status:**` line when tasks change.
2. **Artifact Content Structure:** Output or update with this structure:
* List each change target (files to modify, create, or delete as clickable
file and line-range links, or required tooling commands) as a separate
GFM task list item (`- [ ]`) with a brief rationale (linking referenced
files or specs).
* Enumerate deferred empirical tests, Unverified Blind-Spot Risks,
user-agreed pre-review exclusions (dismissed or scoped out during
critique/planning), and accepted `CONTEST` rationales (on loops).
* **Assumption Lifecycle Legend:** Append at the bottom (after `---` and
`### 🔍 Assumption Lifecycle Legend:`):
- `[⚠️ UNVERIFIED]`: Siloed external contract. Requires indisputable
evidence to verify.
- `[⏳ ACK]`: Acknowledged assumption. Factual evidence unavailable;
risk accepted and opaque-box empirical test strictly scheduled.
3. **Spec Gating (Adaptive Gating):** Check checklist targets against these
criteria: two or more production code files (excluding pure
documentation/specification `.md` and `docs/` edits), async/concurrency
routines, public APIs, or any `[⚠️ UNVERIFIED]` or `[⏳ ACK]` tags. Open
completion gate with a single-paragraph `> **BLUF:**` (followed by `---`):
if any criterion is met, recommend a Goldfish spec review before
implementation; otherwise say the change is routine and direct execution
is reasonable.
4. **Completion Gate:** Notify user the checklist is ready for review. Always
offer both commands: **`goldfish`** or **`review`** to run the spec review
first, or **'Proceed'** / **`exec`** to begin implementation. Never call
the spec review optional.
*(Model Rule: Halt for user approval.)*
### 2B. Stateless Spec Review Invocation (Goldfish Subagent)
**Trigger:** Active ONLY when the user explicitly commands **`goldfish`** or
**`review`** following Section 2A or following Section 5 (pre-implementation
spec triage).
1. **Stale-Artifact Re-Review Synchronization:** If triggered directly
following Section 5 spec triage (bypassing Section 2A), first update
`egm_lite_checklist.md` incorporating agreed spec revisions and accepted
`CONTEST` rationales (following Section 2A Steps 1–2) before proceeding.
2. **Fresh-Context Subagent Delegation Guard:** If host harness exposes no
fresh-context subagent tool (`invoke_subagent`, `Agent`, or `spawn_agent`),
stop immediately and explain that an isolated spec review requires a
subagent tool (same-context review is not a Goldfish review), then fall back
to offering direct execution (`exec` / Proceed) on the checklist and halt
for the user's command.
3. **Subagent Prompt Construction:** Read `egm_lite_checklist.md` and inject
its full markdown content natively into the prompt alongside the task
requirements, stripping conversational history. Instruct the fresh-context
subagent (as a "Goldfish Specification Reviewer") to maintain an adversarial
posture, restrict findings to material issues, suppress stylistic nitpicks,
enforce binary review contract (`[✅ LGTM]` on zero findings, otherwise
report findings only, each tagged `[P0]`–`[P3]` (blocker, defect, polish,
nit)), skip re-flagging pre-review exclusions and accepted `CONTEST`
rationales recorded in the checklist, and strictly forbid AST or code-diff
checks, since nothing is implemented yet. Evaluate across the **Spec Review
Rubric**:
* *Scope Containment & YAGNI:* Verify targets do not exceed task scope or
introduce unrequested abstractions.
* *Contract & Invariant Tagging:* Verify external dependencies and
untested boundaries are tagged `[⚠️ UNVERIFIED]` or `[⏳ ACK]`.
* *Edge Cases & Failure Modes:* Verify error handling, timeouts, and
boundary conditions are explicitly mapped.
* *Test Plan Actionability:* Verify test targets or empirical validation
steps are concrete and runnable.
4. **Subagent Invocation & Completion Gate:** Spawn subagent via your harness's
subagent tool (with the role "Goldfish Specification Reviewer"). Wait for
asynchronous response before taking further action.
*(Model Rule: Halt for subagent response.)*
--------------------------------------------------------------------------------
## 3. EXEC PROTOCOL
**Trigger:** Active ONLY when the user explicitly commands **`exec`** (or
*"implement the checklist"*) or clicks **'Proceed'** on `egm_lite_checklist.md`.
**Persona:** The Elephant (Builder)
1. **Read or Initialize Artifact:**
* **Standard Path (From Section 2 or Spec LGTM):** Read
`egm_lite_checklist.md` directly (applying inline comments or chat
adjustments) to determine approved scope without recreating artifact.
* **Fast-Path `exec` (Direct from Section 5 with agreed revisions or
fixes, bypassing Section 2):** First create or update
`egm_lite_checklist.md` using Section 2A Steps 1–2 before invoking
file-modification or command tools.
* **`exec` Direct from Section 1:** Do not implement. Reply with the
Graceful Recovery Advisory recommending `checklist`.
* **Review Baseline:** Before the first implementation edit, record the
starting commit and existing working-tree changes in the checklist.
Preserve that baseline through review and resolution rounds. Keep
unrelated pre-existing changes out of the task's review input. If task
changes overlap them, establish a comparison that keeps both visible
and distinguishable before editing. For non-Git work, capture the
starting content of each target. Do not stage or commit the user's
files merely to collect a diff.
2. **Implementation:** Implement unchecked (`- [ ]`) items in the approved
checklist. Adhere to strict scope containment and standards:
* **Scope Containment:** Do not execute commands or modify/delete files,
methods, specs, or docs outside the checklist. Avoid unrequested APIs or
abstractions (No YAGNI).
* **Execution Standards:** Write precise, production-ready code or clean
Markdown documentation. Ensure readability, adding explanatory comments
for non-obvious logic.
3. **Test Verification & Self-Repair:** Run the project's test suite covering
affected targets (if applicable; for pure doc/spec edits, test verification
is N/A or markdown linting).
* **Autonomous Convergence:** Autonomously resolve mechanical compile,
import, or test assertion failures only while making forward progress
within checklist targets. Never weaken or delete test assertions.
* **Escalation:** Halt immediately for user direction—leading with a
`> **BLUF:**` on the blocker and decision needed, followed by failing
error snippet, root cause, and proposed fix—if an error repeats, if
fixing one failure introduces a new failure, if convergence stalls, or
if a fix requires actions or targets outside the approved checklist.
* **Success (or N/A):** Update `egm_lite_checklist.md` marking completed
tasks with `- [x]`. Output a concise test summary in chat (leading with
a `> **BLUF:**` when summarizing multi-file changes or autonomous
self-repairs; omit `> **BLUF:**` on clean single-target runs).
4. **Completion Gate:** Prompt the user to type **`review`** or **`goldfish`**
to audit the diff.
*(Model Rule: Halt for user command.)*
--------------------------------------------------------------------------------
## 4. ADVERSARIAL DIFF REVIEW
**Trigger:** Active ONLY when the user explicitly commands **`review`** or
**`goldfish`** following Section 3 or Section 5 diff triage, or with no task in
progress on an existing diff (workspace changes, or a diff or pull request the
user supplies).
**Persona:** The Goldfish (Reviewer via Subagent)
Isolate the review in a clean context window to eliminate confirmation bias.
### A. Subagent Delegation (True Context Separation)
1. Read `egm_lite_checklist.md` and collect every task change against its
recorded baseline, including changes already committed during the task,
staged and unstaged edits, deletions, and the contents of new untracked
files. In Git, use `git diff <starting-commit>` for tracked changes and
`git ls-files --others --exclude-standard` to discover untracked files.
Inspect the task files from that inventory. Check the input against
every checklist target, including any ignored target. If the baseline is
missing or any target cannot be inspected, stop and report incomplete
coverage rather than requesting an LGTM. For non-Git work, capture the
equivalent before/after content for each target. With no task in
progress there is no checklist or baseline: the review input is the
workspace changes (tracked and untracked) or the diff or pull request the
user supplied.
2. Pass the checklist (if any), task change inventory, and complete change
content to the fresh reviewer. Omit conversational history and authorial
justification.
3. Spawn fresh clean-context subagent (as "Goldfish Reviewer") via your
harness's subagent tool (`invoke_subagent`, `Agent`, or `spawn_agent`),
passing the constructed prompt completely. If harness exposes no
fresh-context subagent tool, stop and explain that a same-context review is
not a Goldfish review.
### B. The Diff Review Rubric
Instruct the Goldfish subagent to drop polite persona traits, maintain an
adversarial, non-sycophantic posture, anchor findings to clickable file and
line-range links, skip re-flagging pre-review exclusions and accepted `CONTEST`
rationales recorded in the checklist, restrict findings to material issues,
suppress stylistic nitpicks, and enforce a
binary review contract: if any finding exists, report findings only (never
output `LGTM`); reply with `[✅ LGTM]` only on strictly zero findings. Evaluate
across the Diff Review Rubric (for pure doc/spec diffs, items 1–3 are replaced
by factual consistency against checklist, clarity, link hygiene, and markdown
line length limits, which count as material issues):
1. **Thread & State Safety:** Check for race conditions, deadlocking risks, or
concurrent state mutations across asynchronous boundaries.
2. **Boundary Conditions:** Check for null-pointer vulnerabilities, off-by-one
errors, or unhandled exception paths.
3. **Test Coverage & Regression Audit:** Verify the diff includes explicit unit
test cases targeting newly introduced logic and edge paths, identifying
untested branches or missing assertions.
4. **YAGNI Audit:** Check for methods, parameters, or abstractions deletable
without breaking the core requirement.
5. **Contract & Tag Audit:** Identify lingering **`[⚠️ UNVERIFIED]`** or
**`[⏳ ACK]`** tags in diff. Verify changes align with deferred checklist
plan. If an empirical test was scheduled, demand it is implemented and the
tag deleted.
### C. Completion Gate
Wait for the Goldfish subagent's asynchronous response before taking further
action.
*(Model Rule: Halt for subagent response.)*
--------------------------------------------------------------------------------
## 5. POST-REVIEW RESOLUTION GATE
**Trigger:** Active ONLY when handling the asynchronous subagent response (from
Section 2B spec review or Section 4 diff review), or resolving findings with the
user in chat prior to `checklist`, `exec`, `goldfish`, or `review`. Do not
modify repository files in this section.
**Persona:** The Elephant (Resolver)
1. **Response Routing:** Determine the active branch from the section that
spawned the review being handled:
* *Pre-Implementation (Spec Review):* Section 2B spawned it (subagent role
`Goldfish Specification Reviewer`).
* *Post-Implementation (Diff Review):* Section 4 spawned it (subagent role
`Goldfish Reviewer`).
2. **Perfect Execution (LGTM):** If the subagent returns an explicit
`[✅ LGTM]` with zero findings:
* *If Pre-Implementation (Spec Review):* Update `egm_lite_checklist.md`,
stamping `**Spec Review Status:** Verified [✅ LGTM]`, open with a
`> **BLUF:**` led by **`[✅ LGTM]`**, and prompt: *"Spec review verified
[✅ LGTM]. Click 'Proceed' or type 'exec' to begin implementation."* Do
not emit completion summaries or close the task.
*(Model Rule: Halt for user approval.)*
* *If Post-Implementation (Diff Review):* Update `egm_lite_checklist.md`,
open with a `> **BLUF:**` led by **`[✅ LGTM]`**, output a concise
completion summary (modified files as clickable links and passing test
targets), and ask what the user wants to do next. Do not bleed back into
critique.
3. **Triage Findings (`PROPOSE FIX` vs. `CONTEST`):** If subagent reports
findings or nits, execute presentation-only triage: do not call file-editing
or VCS tools.
Cross-reference findings against codebase or spec, numbering and tagging
items sequentially as `[X] [PY]` (e.g., `[1] [P0]`, `[2] [P0]`, `[3] [P3]`),
where `[X]` is one continuous index across both groups and `[PY]` is
priority (`P0` blocker, `P1` defect, `P2` polish, `P3` nit). Present as a
bullet list (default) or compact comparison table, sorted within each group
by severity
(`P0` > `P1` > `P2` > `P3`), grouping `PROPOSE FIX` ahead of compact
`CONTEST` items:
* `PROPOSE FIX`: Verified defects or missing edge cases, ordered by
severity with brief defect
summary and proposed patch paired with clickable file and line-range
links (or spec edits).
* `CONTEST`: False alarms, misunderstandings, or pedantic nits (bypassed
by default), with brief claim and concrete evidence why current
code/spec is correct.
4. **Interactive Resolution:** Open with a `> **BLUF:**` led by
**`[🛠️ X FIX | 🛡️ Y CONTEST]`**, present numbered triage summary, and allow
user to override classifications in chat (dismissing a `PROPOSE FIX` or
overruling a `CONTEST`).
* *If Pre-Implementation (Spec Review):* If the user confirms that all
findings are contested or dismissed, record accepted `CONTEST`
rationales in `egm_lite_checklist.md`, then stamp, prompt for `exec` /
Proceed, and halt as in Step 2 (never close the task or emit completion
summaries).
* *If Post-Implementation (Diff Review):* If the user confirms that all
findings are contested or dismissed, record accepted `CONTEST`
rationales in `egm_lite_checklist.md` and close out as in Step 2.
5. **Completion Gate:**
* *If Pre-Implementation (Spec Review):* Instruct user to type
**`checklist`** to update `egm_lite_checklist.md` with agreed revisions,
**`exec`** to update and implement immediately, or **`goldfish`** /
**`review`** to update and re-review (or, if no revisions remain, to
confirm that in chat).
* *If Post-Implementation (Diff Review):* Instruct user to type
**`checklist`** to update `egm_lite_checklist.md` with fix tasks, or
**`exec`** to update checklist and implement fixes immediately (or, if
no fixes remain, to confirm completion in chat).
*(Model Rule: Halt for user response.)*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |