Elephant-Goldfish Model plugin
Google plugin for designing with an agent: the elephant drafts a spec, goldfish reviewers check it without the conversation
- 17,901 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The skills create and edit files in the repository: the brief, the draft and documentation
- Reviewer subagents read the project source that the document references
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/elephant-goldfish-modelDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skills create and edit files in the repository: the brief, the draft and documentation
- Reviewer subagents read the project source that the document references
This is third-party code. Review the repository files before installing.
What it does
Elephant-Goldfish Model (EGM) is a plugin with a set of skills for working on a specification before any code. The elephant is the agent that holds project context, requirements and earlier decisions and drafts the design. The goldfish are reviewer subagents: they see only the document and the source it references, without the earlier conversation, so they catch unstated assumptions and blind spots. Architectural trade-offs and approval stay with you. The plugin has seven skills. `egm-brainstorm` tests an idea and writes `concepts_brief.md`, and `egm-draft` turns a brief or notes into `design_draft.md`, pausing after each section for your feedback. `egm-review` runs the draft through fresh reviewers in five stages, `egm-review-loop` runs a configured group of reviewers, and `egm-resolve` helps work through findings. `egm-bootstrap` creates or updates documentation for an existing codebase, and `egm-drift-report` compares checked-in documents with the current source.
Who it is for. For developers and tech leads who want to agree a feature design with an agent before building and get the document reviewed with fresh eyes.
Good fit when
- A new feature needs design decisions before code, such as webhook delivery with retries and duplicate events
- A draft spec needs a review with fresh eyes and no accumulated context
- You need to create or update documentation for an existing codebase
- You need to find gaps between checked-in documents and the current code
Not a fit when
- A small, clear bug fix: your normal workflow is enough for it
- You want a finished implementation: the plugin drafts and reviews the design, and you ask the agent to code it after approval
- You do not want to approve the document step by step: `egm-draft` pauses after every section for your feedback
Example request
/egm:egm-brainstorm Add webhook delivery to this projectLimitations
In Antigravity and Claude Code, commands need the `/egm:` prefix, for example `/egm:egm-brainstorm`. On Antigravity CLI 1.4.8 an unprefixed name is not completed, while 1.4.10 completes it to the prefixed command. Install the whole plugin: the skills read reviewer prompts and document standards from its files. Start a new session after installing. Claude Cowork and ChatGPT Work have a separate setup guide in `docs/harnesses.md`.
How to disable. Disable the plugin with your agent's tools, in Claude Code with `claude plugin uninstall egm@egm`. Generated documents such as `concepts_brief.md`, `design_draft.md` and `docs/designs/` stay in the repository; delete them by hand.
FAQ
How do I install EGM in Claude Code?
Run `claude plugin marketplace add google/elephant-goldfish-model`, then `claude plugin install egm@egm`, and start a new session.
Do I have to run the skills in order?
No. Each skill works on its own; the brainstorm, draft, review sequence is only for the full design cycle.
Where does EGM keep its results?
The brief goes to `concepts_brief.md`, the draft to `design_draft.md`, and approved specifications are suggested for `docs/designs/`.
Which agents does EGM work with?
Claude Code, Codex and Antigravity (CLI, app and the Visual Studio Code extension).
Why do EGM reviewers work without the conversation context?
That way they see only the document and the source it references. Assumptions that look obvious to the author stand out without that context.
Discussion
No questions or reviews yet.
Related
PluginsSix commands for Claude Code, Codex and Cursor: the main session holds context while fresh agents review the problem and diff.
Skills for spec-driven development: brainstorming, planning, debate-style review and idea grilling before the first commit.
A 33-skill plugin with gates: question the request, verify facts against sources, test first, review by a second model
A plugin with three skills for large development work: project analysis, phased tasks tracked as GitHub Issues, parallel agents and code review
A Claude Code plugin that extracts behavioral specs, test vectors and acceptance criteria from a codebase, with a provenance trail
A plugin with 22 skills for system design: from load estimates to failure analysis, a /design command and an orchestrator agent.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Elephant-Goldfish Model (this card) | yes | 17,901 | |
| Superpowers | no | 316,679 | sets a general development process with tests and subagents, while EGM focuses on the spec and its review by context-free reviewers |
| Spec Kit | no | 149,434 | drives development from a spec through CLI commands, while EGM adds review of the document by fresh reviewers |
README in short
A Google open-source repository under Apache-2.0. The idea comes from Dave Rensin's essay on elephants and goldfish. Architecture and test records live in `docs/` and `TESTING.md`.