Egm Drift Report

google/elephant-goldfish-model/skills/egm-drift-report

by google72d06f52a2482885d9a64bd24b291c6e8628942cApache-2.021K starsListed Nov 17, 2026Updated Nov 17, 2026Repository updated today

Runs drift detection on all design documents to check for document and code consistency. Produces an actionable report with differences. Use when the user asks to detect drift or check for consistency across all design documents or READMEs in a directory.

AI-generated overview

Compares design documents and READMEs against the codebase and writes a markdown report of every divergence found.

What it does
For each design document or README in a target directory, the skill reads the document's intent, proposed changes and named files or symbols, locates the corresponding source code, and compares the two. It flags missing features, incomplete data models, hardcoded logic shortcuts and architectural divergence, reporting only mismatches. Results are appended per document to a dated DRIFT_REPORT.md file in a fixed heading-and-bullets format, or marked "No drift detected."
When to use it
Use when the user asks to detect drift or check consistency between design documents or READMEs and the implementation in a directory. Also suited to auditing whether planned specifications were actually implemented.
Requirements
Instructions only, no bundled scripts. Needs a target directory of design documents or READMEs, read access to the source tree, code search or grep, and a file-writing tool to create the report.

Detect Drift In Designs and Code

When running in Codex or ChatGPT Work, first read Codex integration. In Claude Code or Cowork, read ${CLAUDE_PLUGIN_ROOT}/docs/claude.md first.

When the user asks to detect drift across all designs or a set of READMEs, the goal is to identify all instances where the codebase has diverged or failed to implement the specifications described by those designs or READMEs.

  1. Check Input: Verify a directory containing design documents or READMEs is provided. If not provided, ask the user to specify the target directory.

  2. List Documents: List all files in the design directory.

  3. Analyze: For EACH design document:

    • Contextualize: Read the design document. Identify the intent, proposed changes, and specific filenames/symbols mentioned.
    • Locate Source: Find the corresponding source code files in the source tree. If paths aren't explicit, use code search or grep to locate the relevant classes, functions, or API endpoints mentioned in the doc. Prompt the user to add missing links to the document to make future detection cheaper.
    • Verify: Read the current state of those source files.
    • Detect Drift: Compare the design vs. reality. Look specifically for:
      • Missing Features: Logic described in the doc but absent in the code.
      • Incomplete Models: Dataclasses/Classes/Structs/Protos missing fields specified in the design.
      • Logic Shortcuts: Hardcoded values where dynamic logic was planned.
      • Architectural Divergence: Implementation using different patterns/libraries than proposed.
    • Filter: Report ONLY the differences. Do not describe what is working or what matches. If the code matches the design perfectly, output "No drift detected."
  4. Report: Produce a single report listing all discrepancies found.

    • Append the analysis for each file to {YYYY-MM-DD}_DRIFT_REPORT.md using your file-writing tool.

    • Strict Format:

      markdown
      ## <DESIGN_DOC_NAME>
      <Bulleted list of specific divergences found><Or "No drift detected">
  5. Guidance

    • Be rigorous. If a design doc mentions a specific object, field or file name and the code doesn't have it, that is a reportable drift. Double check for coverage. If there is some part of the logic that is not referenced in a design or README, this is a reportable drift.
    • Read files liberally to ensure you are looking at the current state of the code, not relying on memory.
    • Process the files sequentially to ensure the tool output buffer doesn't overflow.

Source and attribution

Source:google/elephant-goldfish-modelinskills/egm-drift-reportat commit72d06f5

License: Apache-2.0

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Add a badge to your README

Show readers this skill is listed on SourceWeft. The badge links to this page.

Preview of the “Listed on SourceWeft” badge
[![Listed on SourceWeft](https://sourceweft.com/badge/skills/gh-google-elephant-goldfish-model-egm-drift-report-skills-egm-drift-report-a81159be2d1f0fad.svg)](https://sourceweft.com/skills/gh-google-elephant-goldfish-model-egm-drift-report-skills-egm-drift-report-a81159be2d1f0fad?utm_source=readme&utm_medium=badge)

Report or request removal

More from google/elephant-goldfish-model

Egm Resolve

google

Featured

Resolves reviewer deficiency findings on a document: contests, escalates, proposes fixes, and gates edits through user approval.

Writing & Content21Kupdated today

Egm Review Loop

google

Featured

Executes the Antagonistic-Review process from the Elephant-Goldfish Model (EGM) via an automated multi-agent review loop to audit documents against qualitative standards and structural templates, and automatically apply approved fixes. Use when reviewing design docs, READMEs, feature specifications, implementation plans, or verifying document completeness and tone.

Awaiting classification21Kupdated today

Egm Draft

google

Featured

Drafts a design document section-by-section using the concepts brief from egm-brainstorm (or user notes). This is the second step in the Elephant-Goldfish (EGM) feature flow. Use when you are ready to write a design doc after aligning on requirements + solution.

Awaiting classification21Kupdated today

Egm Bootstrap

google

Featured

Generates and corrects EGM-compliant README.md contract files across a repository directory tree using parallel subagents.

Documents & Office21Kupdated today

Egm Brainstorm

google

Featured

Interactive ideation and brainstorming skill for the Elephant & Goldfish Model (EGM). Helps turn half-baked concepts into structured hypotheses via clarifying questions, review, and iterative refinement. Produces an RFC summary for human review or more detailed design with egm-draft.

Awaiting classification21Kupdated today

Egm Review

google

Featured

Orchestrates the EGM Goldfish Review Protocol. Used as part of the EGM process to perform design document reviews. Executes five review phases: Initial Zoom Out Review, Comprehension Review, Design Critique, Intermediate Zoom Out Review, and Implementation Readiness.

Awaiting classification21Kupdated today