← Explore all agents

ARCHITECTURE AND DECISIONS / Seth Hobson

Monorepo architect

Chooses a monorepo tool from the repository's constraints instead of naming one by fashion.

“Expert in monorepo architecture, build systems, and dependency management. Masters Nx, Turborepo, Bazel, and Lerna.”

01 / THE REASONING

Why this made the selection.

  • The workflow says to assess codebase size and team structure before selecting Nx, Turborepo, Bazel, or Lerna.
  • Frontmatter sets model to opus and does not declare tools or a benchmark.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • plugins/developer-essentials/agents/monorepo-architect.md
  • LICENSE
  • Round 2: pinned definition, output contract and permission/dependency boundaries reread on 2026-10-14

Our findings

  • Frontmatter name is monorepo-architect and model is opus, with no tools key.
  • Capabilities name Nx, Turborepo, Bazel, and Lerna as the tool choices.
  • The workflow starts by assessing codebase size and team structure, then selecting tooling.
  • Later steps include build caching, affected or changed detection, task pipelines, and remote caching.
  • The workflow places build caching and affected-change detection before remote cache integration.
  • Dependency tags, focused shared libraries and code ownership are named mechanisms for limiting cross-project coupling.

Not established by this review

  • The agent was not executed against a live repository or host.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗
  1. The pinned file does not state a host install command.
  2. Choose tooling from the existing project constraints and validate cache inputs/outputs on representative changes before enabling remote reuse.

Before you start

  • The repository layout, team structure, and the CI or sharing problem to address.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Agent profile ↗Checked

    https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/developer-essentials/agents/monorepo-architect.md

    Supports: Role and stated limits

  2. Repository licence ↗Checked

    https://github.com/wshobson/agents/blob/46891e7e60da0e52baf1050b7b6391b64e84c6d9/LICENSE

    Supports: Redistribution terms

Evidence & Ask