Cursor subagents: examples, agent teams

Cursor subagents are scoped agent runs delegated from the main thread, each with its own rules, MCP servers, skills, and review expectations. This page explains how to define one, which work to hand it, and how a team keeps every delegated run reviewable. It is the same material we teach in the Cursor workshop.

What teams need before scaling subagents

Subagents create leverage only when teams define clear delegation boundaries, review expectations, and repeatable context. The training focus is not more parallelism by default, but knowing which work can be delegated safely and which Cursor rules, Cursor MCP, skills, or team instructions control the run.

What the workshop installs

Teams leave with shared agent instructions, repository conventions, Cursor code review checklists, and examples for turning repeatable engineering work into skills that engineers can inspect and improve.

How we measure success

The target is smaller review burden, faster setup on real tasks, fewer abandoned agent runs, and clearer rules for when engineers delegate, review, or own the work themselves.

Official references

Current product documentation we use when shaping this training topic.

Related training topics

Bring this into your team

We tailor the training to your codebase, adoption stage, and review standards.

Book a 15-minute sync