project-structure-validator

To validate project modularity, stress-test your structure file against architectural principles to assess module independence and detect overlapping responsibilities. This ensures feasible module definitions and reduces future refactoring efforts early in implementation planning.

Detect circular dependencies in your project structure by analyzing the defined modules for interdependencies that form loops. This validation process identifies circular references and highlights modules with unclear boundaries before you commit to the architecture.

Identifying modules with overlapping responsibilities involves analyzing your project structure to find boundaries where multiple modules perform similar tasks. This architectural validation process detects unclear module definitions and ensures each component maintains strict independence.

You need to run a dependency analysis when committing to a complex project structure during implementation planning. This process stress-tests proposed module breakdowns to ensure clear purposes and minimal interdependencies, preventing architectural issues early.

Project structure validation requires a markdown file defining your proposed modules, typically located at spec/implementation/project_structure.md. The validator assesses this file against architectural principles to detect circular dependencies and unclear module boundaries.