gsd-intel

You can check codebase intelligence freshness by reviewing the status and diff information stored in .planning/intel/ to determine whether the index reflects current repository changes or requires a refresh.

Searching indexed analysis terms involves querying the codebase intelligence entries in .planning/intel/ to retrieve matching notes and architecture summaries without scanning the entire codebase manually.

To rebuild codebase intelligence indexes, trigger a refresh operation that regenerates architecture, dependency, and file-role summary files by parsing project data and spawning controlled tasks for deterministic updates.

Yes, this codebase indexing approach operates with no external dependencies, requiring only direct access to project files, JSON parsing capabilities, and timestamp tracking to manage intelligence files.

Codebase intelligence snapshot diffs can appear due to timestamp tracking inconsistencies or controlled task spawning variations during deterministic intel updates, requiring an index rebuild to synchronize the stored state.

You need to refresh codebase architecture and dependency data when the repository structure changes significantly, ensuring the intelligence index in .planning/intel/ accurately reflects current file roles and dependency relationships.