kc-plugin-forge-doc-sync

Automate plugin documentation alignment by running a multi-phase workflow that statically scans source files, enriches history, and updates docs to prevent documentation drift. This process validates SKILL.md, hooks, and cross-references against the actual codebase.

Documentation drift occurs when docs become outdated relative to code. Static analysis detects these gaps by inventorying source files and docs, categorizing discrepancies during history enrichment, and driving automated updates to keep knowledge management accurate.

Validate SKILL.md, hooks, and cross-references by executing a static scan phase that inventories source files and docs. This phase categorizes alignment gaps and ensures plugin documentation accurately reflects the current codebase state.

Yes, doc-sync supports the kc-plugin-forge ecosystem by applying a phase-driven workflow. It performs static scans, history enrichment, write and update phases, live probes, and self-updates to automatically generate gap reports and align documentation.

The best way to report documentation gaps is through history-enriched static analysis. This approach inventories source files, categorizes doc drift gaps across multiple workflow phases, and outputs actionable reports to drive documentation improvements.

Documentation drift happens when code changes outpace manual updates. You need automated doc-sync when managing plugins in the kc-plugin-forge ecosystem to validate hooks and docs during static scans, ensuring cross-references remain consistently aligned.