What problem does it solve? Turning functional requirements into a sound modular architecture is hard: teams often end up with distributed monoliths or big balls of mud because coupling decisions are made ad hoc. This Skill guides an agent through a structured, approval-gated process that produces validated module boundaries, design documents, and test specifications grounded in the Balanced Coupling model. ## Core Features & Use Cases - Coupling-aware architecture design: Classifies subdomains (core/supporting/generic), assesses integration strength, distance, and volatility, and applies the balance rule to flag unbalanced coupling. - Complete design documentation: Generates per-module design.md files with responsibilities, encapsulated knowledge, integration contracts, and change vectors, plus an overall architecture.md. - Module test specifications: Produces unit, contract, boundary, and behavior test specs for every module, ready for developers to implement. - Use Case: You have a functional requirements document for a new ordering system. Run this Skill to iteratively validate subdomain classifications, design module boundaries, and receive a full docs/design folder with architecture, module designs, and test specs. ## Quick Start Use the modularity-design skill with docs/requirements.md to design the system architecture and produce module design documents.
