--- name: egm-drift-report license: Apache-2.0 disable-model-invocation: true description: >- 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. --- # Detect Drift In Designs and Code Before any work, read [Copilot integration](../../docs/copilot.md), including when this skill is invoked directly. Its host adaptation applies to delegation, paths, questions and synthesis throughout this workflow. 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 or an explicit list of design documents or contracts is provided. If missing, ask for the target scope. 2. **List Documents**: Enumerate the requested directory, or use exactly the supplied file list (for example the contracts returned by bootstrap). Do not expand an explicit list to unrelated documents. 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 ## ``` 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.