Lite Deepen

Surface architectural friction and propose deepening opportunities — changes that turn shallow modules into deep ones. Aim at testability and navigability, not tidiness.

The run happens in chat: scope → explore → cards → grill → brief. It writes only the brief and the two target-repo side effects the user approves during the grill.

Tone

Read VOCABULARY.md before you write a card. Use these words, with these meanings, exactly: module, interface, implementation, depth, deep, shallow, seam, adapter, leverage, locality.

Never substitute a near-synonym:

Domain nouns come from the target repo's own glossary: if its CONTEXT.md defines "Order", say "the Order intake module", not "the FooBarHandler" or "the Order service".