context-synchronization

To synchronize product documentation after a Conductor track completes, load the completed track specification and apply proposed changes to conductor/product.md, conductor/product-guidelines.md, and conductor/tech-stack.md with user confirmation before committing.

You should update project-level tech-stack and guidelines documentation when a track reaches completed status and the implement task has finished, ensuring central docs reflect the latest track specifications.

Documentation impact analysis works by loading the track specification from conductor/tracks/<track_id>/spec.md, analyzing the specification's effects on existing docs, and proposing specific updates to product, guidelines, and tech-stack files before applying them.

Yes, you can review proposed documentation changes before they are committed. The synchronization process analyzes impacts, proposes updates to central docs, and requires explicit user confirmation before applying and committing the modifications.

No, you do not need to manually update conductor/product.md after finishing an implement task. Automated synchronization loads the completed track spec, proposes documentation updates, and commits the changes after you confirm them.

The best way to maintain traceability for product docs and track specifications is to commit documentation updates immediately after synchronization, linking the completed track spec changes directly to the revised product, guidelines, and tech-stack markdown files.