What problem does it solve? Software projects often grow into tangled codebases where modules lack clear responsibilities, circular dependencies appear, and shared folders become dumping grounds. This Skill gives a Technical Product Owner agent concrete guidelines, templates, and review checklists to plan and audit module structure so the project stays understandable for humans and AI agents. ## Core Features & Use Cases - Module Structure Planning: Provides recommended directory layouts for modular monoliths, backend-heavy, and frontend-heavy projects, plus a module plan template covering dependencies, public interfaces, and integration adapters. - Boundary Enforcement Rules: Defines five boundary rules covering inward imports, shared-folder discipline, infrastructure adapters, dependency direction, and single data ownership per entity. - Review Checklists and Templates: Ships a module README template, split/merge decision criteria, and a review checklist for validating module quality. - Use Case: When starting a new MVP, ask the agent to produce a module plan; it will output a module list with responsibilities, data ownership, dependency map, and risky boundaries that developers can implement against. ## Quick Start Ask the agent to create a module structure plan for your project using the module structure guidelines, including the module list, dependency map, and public interfaces.
