qsd-map-codebase

Mapping an unfamiliar codebase is done by running parallel mapper agents that analyze the repository and write seven structured documents, including STACK.md and ARCHITECTURE.md, directly to .planning/codebase/.

Creating a codebase map for brownfield onboarding involves spawning four parallel mapper agents that generate seven structured documents covering architecture, conventions, and testing, resulting in a commit-ready map under .planning/codebase/.

Yes, you can use parallel agents to document an existing project structure automatically. The mapping pipeline enforces a four-agent parallel process that writes seven structured documents and verifies their presence before completing a commit-ready map.

Mapping a codebase generates seven structured documents: STACK.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, INTEGRATIONS.md, and CONCERNS.md, all written directly to the .planning/codebase/ directory.

Auditing and updating codebase documentation after significant changes is handled by rerunning the map-codebase workflow, which overwrites the seven existing structured documents in .planning/codebase/ with fresh analysis from the parallel mapper agents.