Repository Strategy

Use to decide how a project's applications are organized into repositories — single repo, monorepo, or multiple repos — based on shared code, coupling, team boundaries, and release cadence. A decision, not a default; feeds monorepo-selection when a monorepo is chosen.

ahtishamshahzad Updated 0 repo stars

File contents

ahtishamshahzad/agent_dev_flow commit fd63c16d3b

Frequently asked questions

npx get-skill add ahtishamshahzad/repository-strategy