DOCUMENT_PROJECT_STATE

Document a legacy codebase architecture for onboarding by analyzing real repository files to map project structure, tech stack, and technical debt. This process generates a comprehensive architecture document with versioned dependencies and debt warnings to accelerate team onboarding.

The best way to capture technical debt in an existing project is through deep analysis of key files like configuration, data models, and APIs. This yields a structured architecture document that highlights debt warnings and critical codebase patterns for long-term maintenance.

Generate an architecture document with exact tech stack versions by running automated discovery on project files like package.json and README.md. This maps the system and produces a validated markdown file detailing your tech stack, key patterns, and critical files.

Yes, you can automatically map a project structure from real repository files. The system performs automated discovery on files like package.json and the src/ layout to map the system, validates against the real repository, and generates a structured architecture doc.

A codebase architecture document should include a project overview, exact tech stack versions, key patterns, critical files, and technical debt warnings. Drafting this comprehensive document relies on deep analysis of entry points, configuration, data models, and APIs.

Yes, this approach works for documenting legacy code without existing documentation by guiding engineers through discovery, analysis, and drafting. It applies reality-based analysis to surface critical details and generate a lean architecture document.