architecture-deepening

What problem does it solve?

Shallow module interfaces force callers to understand internals, coordinate across modules, and manage complexity that should live behind a better abstraction.

Core Features & Use Cases

• Find shallow modules by analyzing interface-to-implementation shallowness signals across the codebase, without treating this as a bug/style review.
• Identify seams for deepening (data, protocol, temporal) to determine where responsibility can be moved behind a cleaner interface.
• Design and converge on deepening decisions through candidate exploration, interface alternative proposals, and an iterative collaboration process with explicit trade-offs and a documented deepening decision.
• Use cases: recurring “how do I use this?” confusion, new contributor onboarding, pre–major feature architecture improvement, and post–defect-fix follow-up after running a full-repo defects review.

Quick Start

Ask your agent to architecture-deepen by running the command architecture-deepening and targeting areas that feel confusing or internally leaky so it can propose deepened module interfaces.