xddp.codemap

To generate a module catalog, the skill scans your repository via directory traversal and source code parsing to map internal module relationships and exported symbols. It creates a comprehensive index of public symbols and dependency graphs for architectural analysis.

A dependency graph maps internal module relationships within a codebase. It facilitates architectural analysis by providing a clear visualization of module dependencies, which is essential for effective XDDP execution and BFS-based specification prioritization.

Yes, you can visualize module relationships using Mermaid-based dependency diagrams. The skill generates these diagrams automatically during the cataloging process to help you understand the architectural structure and internal dependencies of your software repository.

You map out your current architecture by executing the cataloging skill to scan the codebase, ensuring that impact analysis and specification tasks are grounded in the actual repository structure. This maintains an up-to-date understanding for effective XDDP execution.

The best way to maintain an up-to-date understanding is through automated cataloging that scans repositories to identify modules, public symbols, and internal dependency graphs. This ensures your architectural analysis reflects the actual codebase structure during XDDP workflows.

Yes, BFS-based task prioritization requires a comprehensive module catalog including symbol indices and dependency graphs. Parsing the source code to map exported symbols ensures that specification tasks are accurately prioritized based on actual module relationships.