WHEN TO USE: When the team is growing and the current repo structure is causing friction..

You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: System Design & Architecture
- Use case: WHEN TO USE: When the team is growing and the current repo structure is causing friction.
- Source task:
  - Monorepo vs. Multi-repo Decision Framework
  - Act as a software engineering advisor. My team is {{team_size}} engineers working on {{number_of_services_apps}}. We are deciding between monorepo and multi-repo. Analyse both approaches for our context and produce:
  - 1. a comparison table across dimensions: build speed, code sharing, dependency management, CI/CD complexity, team autonomy, and onboarding
  - 2. the recommendation best suited to our size and team structure
  - 3. tooling options if we choose monorepo (Nx, Turborepo, Lerna, Bazel : fit for our stack: {{stack}})
  - 4. a migration plan if we need to consolidate from multi-repo

# Goal
Comparison table, a recommendation with rationale, tooling guide for the recommended approach, and a migration plan.

# Constraints
- Produce a complete, usable first draft in one response.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Comparison table, a recommendation with rationale, tooling guide for the recommended approach, and a migration plan.