modular-skills-architect

To refactor an agent ecosystem, you must first map dependencies between skills, commands, and documentation to generate an actionable plan. This approach outputs concrete steps to split, consolidate, rename, or delete components for better maintainability and clear ownership.

Agent ecosystem mapping visualizes the relationships and dependencies across your agent's skills, commands, workflows, and hooks. You need it when components become difficult to understand, allowing you to untangle them and establish a more robust architecture.

To consolidate or split agent skills and workflows, generate a refactoring plan that analyzes routing and ownership consistency. This yields a module design specifying which components to merge, separate, rename, or delete for optimal architecture.

Yes, you can fix agent routing and ownership consistency issues by mapping the context ecosystem across agent files and documentation. This identifies inconsistencies and produces a targeted refactoring plan to resolve component ownership conflicts.

The best way to visualize dependencies between agent commands and hooks is through system mapping. This process diagrams the interconnected context ecosystem, revealing structural relationships so you can define clear ownership and improve routing.

Inconsistent component ownership and routing in agent architecture happens when interconnected skills, commands, and documentation grow without centralized mapping. Addressing this requires an ecosystem analysis to untangle dependencies and define clear ownership boundaries.