doc-driftlisted

Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Compare design documents against actual code/configuration, find inconsistencies, and output a prioritized attention list. Arguments: $ARGUMENTS - No arguments: scan all modules - `--module <name>`: only check the specified module ## Execution Flow ### 1. Determine Scope Discover the project's documentation and code structure: - Look for design docs in `Docs/`, `Documentation/`, or any directory referenced in `CLAUDE.md` - Look for code modules under `Assets/Scripts/`, `Assets/Plugins/`, `src/`, or the project's main code directories - Group related docs and code into module pairs (e.g., "Player" docs ↔ Player code directory) If the user specified `--module`, only scan that module. Otherwise, group all discovered modules and dispatch parallel subagents (`subagent_type: "general-purpose"`, `model: "opus"`) — one per group (max 5 groups). ### 2. Each Subagent's Task Each subagent prompt must include: 1. The doc paths and code paths for its assigned modules 2. The following review instructions: ``` You are a document-code consistency auditor. Read all rules, states, enums, and numeric parameters defined in the design documents, then search for corresponding implementations in the code and verify each one. Focus on: - Features defined in docs but not implemented in code (entire subsystems or individual features) - Features implemented in code