gsd-intel

Codebase intelligence updates are tracked by analyzing and surfacing gaps in planning intelligence files. This approach enforces a frontmatter-driven discovery structure, relying on explicit intel files under .planning/intel/ to guide extraction and keep architectural and dependency information current.

Maintaining codebase documentation for onboarding is best achieved by centralizing intelligence about structure, APIs, and architecture. By querying and refreshing intel snapshots, new team members can quickly align on the current project state by reviewing the latest data.

Yes, codebase analysis can be automated to detect planning intelligence gaps. The system proactively identifies and surfaces intelligence gaps and updates, enforcing a frontmatter-driven structure to automatically guide extraction and updates across a growing codebase.

Yes, explicit intel files are required to index codebase architecture information. The system relies on specific intel files located within the .planning/intel/ directory to enforce discovery structure and accurately guide the extraction of architectural and dependency data.

Codebase intelligence files should be refreshed when changes occur in the repository to ensure proactive updates. By querying the intel index and refreshing the data when gaps are detected, you keep architectural and dependency information current across the growing codebase.