Google AI Releases Elephant-Goldfish Model Plugin for Spec-First Coding

Google has open-sourced the Elephant-Goldfish Model (EGM) plugin, a design-and-review layer for AI coding agents. The Elephant-Goldfish Model plugin makes an agent write a specification before it writes code. Fresh subagents with no conversation history then attack that spec. Google says thousands of its engineers use it. It is quite simple: catch wrong assumptions in a Markdown file, not in a pull request.

What is Google’s Elephant-Goldfish Model plugin?

EGM is an Apache 2.0 plugin of skills, reviewer personas and document standards. It is not a new language model. The method comes from Dave Rensin’s essay on elephants and goldfish. The Google Open Source blog frames it as a fix for AI “slop” and session context collapse. The README states it is not an officially supported Google product.

How does the Elephant-Goldfish workflow work?

The Elephant is a long session holding project context and earlier decisions. It drafts the spec and writes no code. Each Goldfish is a stateless subagent. It reads only the draft and the files it references. You resolve trade-offs and approve the design.

The core loop has 3 commands:

/egm-brainstorm clarifies the idea, then runs a 6-lens Goldfish swarm. Lenses cover YAGNI, token cost, UX, migration, observability and tech debt. Output: concepts_brief.md.

/egm-draft turns the brief into a design doc under docs/designs/, section by section.

/egm-review runs the Goldfish review.

/egm-drift-report later compares code with the spec. The docs recommend running it weekly.

What happens in the 5-stage Goldfish review?

The review skill runs 5 sequential stages:

Initial Zoom Out: checks the whole document at a high level.

Comprehension Test: a Goldfish paraphrases the design. A wrong paraphrase means the doc is ambiguous.

Critic Review: design, structural and style reviewers hunt gaps and edge cases.

Intermediate Zoom Out: rechecks architecture after fixes.

Implementation Readiness: checks file paths, data structures and signatures.

Each stage allows at most 1 re-audit. Findings are ranked Blocker, Major or Nit. If a host has no subagent tool, EGM stops. A same-context review is not a Goldfish review.

Which coding agents does EGM support?

Launch coverage described Antigravity-only support, with more coming. The current harness guide covers Antigravity CLI and App, Claude Code, Claude Cowork, Codex, ChatGPT, omp and Muse. Antigravity CLI, Claude Code and Codex pass automated end-to-end fixtures.

Claude Code needs version 2.1.271 or later. Reviewers there get only Read, Grep and Glob tools. CLAUDE.md files are excluded from their context.

The test record gives concrete run data:

Antigravity CLI 1.4.5: 16 native reviewers ran, stages in order.

Codex 0.163.0: 15 native reviewers, 2 live tests in 573.13s.

Codex CLI with the v0.1.0 ZIP: full suite passed in 482.30s.

How does EGM compare with Spec Kit, Kiro and Superpowers?

EGM’s distinct move is reviewing the spec with zero-context agents. Spec Kit and Kiro center on human review between phases. Superpowers isolates subagents mainly at implementation time.

Check out the GitHub repo, the project site and the Google Open Source blog post. Also, feel free to follow us on Twitter and don’t forget to join our 150k+ML SubReddit and Subscribe to our Newsletter. Wait! are you on telegram? now you can join us on telegram as well.

Need to partner with us for promoting your GitHub Repo OR Hugging Face Page OR Product Release OR Webinar etc.? Connect with us