egm-drift-report

1# Detect Drift In Designs and Code
2 
3When running in Codex or ChatGPT Work, first read [Codex integration](../../docs/codex.md).
4In Claude Code or Cowork, read `${CLAUDE_PLUGIN_ROOT}/docs/claude.md` first.
5 
6When the user asks to detect drift across all designs or a set of READMEs, the
7goal is to identify all instances where the codebase has diverged or failed to
8implement the specifications described by those designs or READMEs.
9 
101.  **Check Input**: Verify a directory containing design documents or READMEs
11    is provided. If not provided, ask the user to specify the target directory.
122.  **List Documents**: List all files in the design directory.
133.  **Analyze**: For EACH design document:
14 
15    *   **Contextualize**: Read the design document. Identify the intent,
16        proposed changes, and specific filenames/symbols mentioned.
17    *   **Locate Source**: Find the corresponding source code files in the
18        source tree. If paths aren't explicit, use code search or grep to
19        locate the relevant classes, functions, or API endpoints mentioned in
20        the doc. Prompt the user to add missing links to the document to make
21        future detection cheaper.
22    *   **Verify**: Read the current state of those source files.
23    *   **Detect Drift**: Compare the design vs. reality. Look specifically for:
24        *   Missing Features: Logic described in the doc but absent in the code.
25        *   Incomplete Models: Dataclasses/Classes/Structs/Protos missing fields
26…