Component catalog
Patterns you've already built and approved once — a schema for tenancy, an auth flow, an audit trail — become adoptable components instead of code you rewrite per project.
How it works
RepoScanAgent inventories an existing repo into board-ready features and a stack overview — the starting picture of what your team has already built.
A lead promotes an approved db-design into the tenant's schema-component library — tenancy, auth, audit, and similar patterns become adoptable rather than redrawn per project.
DbDesignAgent composes adopted components directly into a new schema design rather than starting from a blank spec.
An approved spec can be promoted to the library at the moment of approval — and forked whole into a new project, so a proven feature definition is a starting point, not a rewrite.
Fork/adopt still runs through the same proposal → gate pipeline as any agent-authored change — nothing vendors into your repo unreviewed.
The agents behind it
Human control
Adoption proposals pass the same gate as any code change; nothing enters your repo without an explicit human approval.