codemap

To generate architecture and onboarding documentation, you map your codebase into seven structured markdown files. This process orchestrates parallel agents against your repository to produce STACK.md, INTEGRATIONS.md, and ARCHITECTURE.md for quick reference.

Documenting project structure and conventions involves creating standardized planning documents like STRUCTURE.md and CONVENTIONS.md. This automated mapping approach uses reusable templates to capture essential onboarding context, bringing new developers up to speed faster.

Automated codebase mapping works by orchestrating parallel agents across an entire repository to capture architecture and onboarding context. It applies reusable templates to write seven planning documents into a designated directory for review.

Yes, you can generate testing and integration documentation without manual writing. The mapping process automatically produces TESTING.md and INTEGRATIONS.md by analyzing your codebase and applying standard templates to capture the required context.

When mapping a repository for architectural clarity, the process creates seven specific files: STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, and CONCERNS.md, all stored within the .planning/codebase/ directory.

Codebase mapping requires no specific dependencies or external components to run. It operates directly on entire repositories, using internal parallel agents and standard templates to write the seven planning documents to your local directory.