doc-architect

Generating a documentation sitemap from your codebase involves scanning the repository using .geminiignore to produce an exhaustive doc sitemap in .agent/workspace/doc_sitemap.json, covering seven article types including reference, guide, and concept.

A complete user documentation sitemap requires seven article types: reference, guide, concept, troubleshooting, tutorial, quickstart, and playbook, with playbooks gated by the presence of a business-use-cases.md file.

Mapping codebase files to a documentation plan requires scanning the repository and ensuring related_files exist in the codebase for every planned article, validating structure and guaranteeing per-section coverage with i18n-friendly slugs.

Yes, you need a business-use-cases.md file to generate playbooks. Playbooks are gated by the presence of this file, while the other six article types like quickstart and tutorial generate regardless.

You should run the doc-architect phase after the doc-ignorer phase to generate the sitemap. This enforces the Phase 2 pipeline sequence: doc-ignorer, doc-architect, doc-writer, then doc-translator.

A valid documentation sitemap must reach the minimum article threshold enforced during generation. The sitemap validates structure, ensures non-overlapping article topics, and guarantees per-section coverage across all seven article types.