eforge-plugin-update-docs

# /eforge-plugin-update-docs Detect documentation drift for a given file or topic, then enqueue an eforge build with a focused prompt describing exactly what needs updating. ## Arguments - `target` (required) - A documentation file path (e.g. `README.md`, `CLAUDE.md`, `docs/api.md`) or a topic keyword (e.g. `architecture`, `readme`, `api`). If not provided, ask the user what they want to update. ## Workflow ### Step 1: Resolve Target File If the argument is a file path, verify it exists. If it's a keyword, search the project for likely matches: - `readme` -> `README.md` - `claude-md` or `claude` -> `CLAUDE.md` - Otherwise, glob for `**/<target>*` and `**/docs/**/<target>*` to find candidates If multiple matches, ask the user to pick one. If none found, report and stop. Read the target file. ### Step 2: Gather Current State Search the codebase to understand what the documentation should reflect. Adapt your search strategy to the document's content: - Read the doc and identify its key claims - file paths, command examples, feature lists, API descriptions, architecture descriptions, agent/component inventories, configuration options - For each category of claim, run targeted searches: - **File paths / directory listings** mentioned in the doc - verify they still exist via Glob - **Commands / scripts** mentioned - check `package.json` scripts, CLI source, or Makefile - **Feature / component inventories** - list the relevant source directories to see what actuall...