Internal Library and Monorepo Dependency Governance
Manage shared code across teams.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Help me create rules for shared code across teams. Interview me one question at a time: (1) how many teams and repositories are involved, (2) what is shared today (libraries, components, configuration, tooling), (3) what has gone wrong (breaking changes, version drift, unclear owners), (4) how releases and versioning work, (5) how teams currently ask for changes to shared code, and (6) what the organization is willing to enforce. My starting notes: [CURRENT_SITUATION]. After the interview, produce a governance proposal including: an ownership model (each shared package has an owner team and a contact); a versioning policy (semantic versioning, deprecation period, supported versions); a change process (proposal, review by affected teams, migration guide); a dependency direction rule (apps depend on libraries, never the reverse; no circular dependencies) with a way to enforce it in the build; compatibility testing across consumers; a catalogue template for shared packages; and a metrics list (version spread, time to adopt, incidents from shared changes). Compare a monorepo versus multi-repo setup for my case with the trade-offs. Highlight the first two rules to adopt this month.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.