sync-docs

You can automate documentation synchronization by running the /sync-docs command, which reads existing markdown files, computes diffs based on source changes, and regenerates targeted documents using standard templates.

The best way to keep docs aligned is to use automated regeneration that preserves unchanged sections of your markdown files and only updates targeted documents driven by change detection after significant feature work.

This process automatically regenerates core markdown documentation files including docs/stack.md, docs/architecture.md, docs/concerns.md, docs/structure.md, and docs/conventions.md based on detected source changes.

No, automated documentation regeneration reads existing markdown files to preserve unchanged sections, ensuring that only targeted documents affected by code changes are updated through standard templates.

You should run documentation synchronization during development and after significant feature work to ensure project docs remain aligned with the evolving source code and accurately reflect structural changes.