gsd-intel

Query codebase architecture by executing inline searches against the .planning/intel directory to retrieve intelligence entries that describe repository structure, dependencies, and mappings. This supports codebase decisions by aggregating relevant architectural insights and file-level metadata into searchable results.

Inspect codebase intelligence status by retrieving file-level metadata from the .planning/intel directory to verify alignment with the latest repository changes. Update the status entries to ensure architectural insights and dependency mappings accurately reflect the current state of the codebase.

Yes, you can refresh the codebase intelligence index by triggering refresh workflows that rebuild and extend the intelligence entries stored in .planning/intel. This process maintains an up-to-date intel index by re-evaluating architectural dependencies and mappings across the entire repository.

Codebase intelligence retrieval works by searching the .planning/intel directory to locate and aggregate intelligence entries that map repository structure and dependencies. Developers execute inline queries to compare architectural insights, ensuring codebase decisions are informed by the latest indexed metadata.

Yes, you need a .planning/intel directory containing your codebase intelligence files to query, inspect, and refresh architectural insights. The workflow searches this specific path to retrieve and update the dependency mappings and structural metadata required for informed codebase decisions.

Refresh the codebase intel index when repository changes occur that invalidate existing architectural insights or dependency mappings. If the .planning/intel entries are already current, executing inline queries is sufficient to retrieve the intelligence needed for codebase decisions without rebuilding the index.