Claude Code skills and team delegation
Adding more subagents rarely speeds a team up; runs get abandoned and review piles up when nobody owns the result. Effective subagents delegation starts with agent boundaries: which tasks delegate safely, and which instructions, MCP, and skills control each run. This guide covers AI team skills and team AI workflows, plus the skill integration that lets engineers inspect and improve delegated work.
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 CLAUDE.md, Claude Code MCP, skills, or team instructions control the run.
What the workshop installs
Teams leave with shared agent instructions, repository conventions, Claude 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.
Selected research
Representative field notes connected to this topic.
Codex workspace agents need repo rules
Codex workspace agents and Claude cloud agents need repo rules: scoped boundary files, connector cards, and replay receipts reviewers can check.
AI coding agents need workflow guardrails
Workflow guardrails for AI coding agents: a precedence clause, a replay mandate, connector cards, and child receipts that keep forks explainable in review.
Claude Code team conventions
Claude Code teams need one shared way to set context, review changes, and keep agent work inside repo rules.
Claude Code 2.1.140: team conventions
Claude Code 2.1.140 team conventions: a skill index for precedence, a hook budget, a CLAUDE TOC, and red-folder approvals reviewers can trace.
MCP training for engineering teams
Practical mcp training for engineering teams using agentic coding, review guardrails, and connector boundaries.
Claude Code team skills and conventions
Claude Code 2.1.150 tightens team conventions around claude code skills, CLAUDE.md, hooks, and shared repo context.
Related training topics
Bring this into your team
We tailor the training to your codebase, adoption stage, and review standards.
Get in touch