invest-backfill

Generate documentation for an undocumented codebase by surveying project files, inferring the technical stack and architecture, and producing context-aware doctrine files like ARCHITECTURE.md. This provides an accurate foundation for future development and onboarding.

Project doctrine scaffolding is the automated creation of foundational context files like VECTOR.md and CLAUDE.md. You need it when you inherit an undocumented codebase and must quickly establish architectural identity, stack conventions, and embedded agent instructions for future development.

Yes, you can perform a dry run to preview inferred architecture files before writing changes. This selective file generation prevents unwanted modifications by letting you review the surveyed project identity, stack, and coding conventions beforehand.

Automated code analysis infers coding conventions by surveying existing project files such as READMEs, package manifests, and config files. It extracts structural signals to generate doctrine that reflects the project's actual reality rather than relying on generic defaults.

Yes, doctrine generation works without external dependencies because it operates directly on the existing codebase. It surveys local project structure and configuration files to infer architecture layers and conventions independently.

The best way to backfill architecture documentation is to run an automated codebase survey that analyzes project identity and stack, then generates contextual doctrine files. This ensures the documentation accurately describes the existing code structure and conventions.