Generate complete codebase documentation

Use Full Tree Documentation to produce a structured, multi-page documentation Space. Its outline organizes the project by topics and reader needs, rather than creating a page for every file.

Configure the run

Choose a connected repository and branch, or a project ZIP. Select the output language and documentation audience. Add a factual project description explaining the product and the reader's purpose.

If you use AI preferences, select the relevant generation workflow before starting. Preferences guide writing; they do not supply missing source facts.

Review before generation

Inspect the proposed documentation structure. Check that it covers the important workflows, modules and interfaces for your audience. Move introductory material ahead of reference detail and remove topics that the project does not support.

Use outline editing to refine names, order and page instructions. On the dedicated generator, continue to the final start step when you are satisfied.

Read the result

Generation creates a Space and fills its pages. Follow the progress shown in the app; duration depends on project size, outline and processing. Do not treat a page title or placeholder as completed content.

When the build finishes, verify key instructions and examples against the project. Edit wording and organization in the Space. Use Update Documentation Gaps for targeted additions or updates after review.

Choose another workflow when appropriate

For a per-file reference, use Codebase Documentation. For a README, release notes or a focused question over selected files, use the corresponding supporting generator.

Generation does not publish a repository change. Exporting to Git is a separate action. Ongoing changes require Autopilot or another explicit update workflow.