context-sync

Synchronizing feature context.md files with session findings automatically merges failure log entries, updates recurring pattern counts, and appends exportable lessons learned to eliminate stale documentation and prevent repeated mistakes.

Feature documentation drifts out of sync because session reviews generate new failure patterns and implementation learnings that require manual updates to the living context document, which often gets neglected during active development workflows.

When feature context files exceed size limits during synchronization, the system automatically archives old entries to keep the living context document manageable and enforces structural validation before writing changes to prevent data loss.

Yes, you can track recurring failure patterns across sessions by maintaining review tracking metadata and flagging pattern threshold alerts within the feature context file to surface recurring issues requiring team-wide attention.

Yes, context synchronization validates the feature context file structure before writing any merged failure logs or lessons learned, ensuring structural integrity and preventing data loss during automated documentation updates.

The best way to eliminate stale documentation in iterative feature development is automatically merging session review findings, failure patterns, and implementation learnings into the feature's living context document after every review cycle.