context-maintenance

To keep project context documentation accurate, you should apply incremental updates to existing context files after tasks are completed. This enforces updating current documents rather than creating duplicates, preventing drift and keeping the context lean.

You should update existing context files versus creating new ones to avoid duplication and stale content. This approach enforces consolidating duplicated information and pruning outdated task artifacts to maintain a lean, non-redundant codebase context.

To promote retrospective lessons into permanent codebase documentation, you move valuable insights from the retrospectives folder into relevant context files. This prevents losing valuable insights and ensures project standards are maintained over time.

The best way to prune stale content and manage task folder lifecycle is to apply periodic consistency checks. This process removes stale task artifacts and consolidates duplicated information to keep documentation concise and non-redundant.

No, this does not handle full codebase-level documentation syncs. It applies to incremental updates after tasks, when new insights are learned, or retrospectives are promoted. For full codebase-level syncs, a context-review approach is needed.

Project context documentation drifts and becomes redundant over time when retrospective insights are not promoted into permanent docs and task artifacts are left unpruned. Applying incremental updates and duplication control prevents this drift.