eforge-plugin-update-docs

Documentation drift detection analyzes your target file or topic to identify stale, missing, or incorrect content, then validates the target exists before composing a focused update prompt to fix the drift.

Yes, you can automate README and CLAUDE.md updates by drift-detecting the documentation and enqueuing a targeted eforge build that generates a precise, PRD-style prompt to sync docs with implementation changes.

Keeping architecture and API docs in sync is handled by identifying documentation drift for the target file, composing a focused PRD-style prompt, and enqueuing an eforge build via the MCP tool to apply the updates.

Yes, this skill applies to any project running eforge, as it validates the target file exists and enqueues the doc-update build through the eforge pipeline via the MCP tool.

The eforge build process fixes stale or missing documentation by validating the target exists, identifying the specific drift, composing a focused PRD-style prompt, and enqueuing the build to report and resolve drift results.

You can check READMEs, CLAUDE.md, docs/api.md, architecture notes, and other targeted docs for drift by providing the target file or topic to begin the drift analysis and build enqueue process.