Team Context Management (TCM) is the practice of curating, sharing, and maintaining AI context at the team level. It bridges personal context management (individual) and enterprise context management (organizational), providing the shared context that enables teams to work effectively with AI.
All levels of context management use the same principles and techniques of context engineering, just applied at different scales. TCM focuses on members, processes, and priorities: the team-specific context that shapes how people collaborate with AI.
## What TCM covers
- **Team members and roles**: who is on the team, their responsibilities, and expertise
- **Processes and workflows**: how the team works, reviews code, handles incidents, ships features
- **Priorities**: what the team is focused on, current sprint goals, quarterly objectives
- **Shared coding standards and conventions**: CLAUDE.md, AGENTS.md, and similar configuration files that encode team-specific rules, style guides, and architectural decisions
- **Shared skills and workflows**: team-level AI skills, templates, and procedures that standardize how AI assists across the team
- **Team memory**: accumulated decisions, lessons learned, and patterns that persist across individual conversations
- **Tool and MCP configurations**: shared tool setups, API integrations, and MCP server configurations
## Why TCM matters
Without TCM, every team member manages their own AI context independently. This leads to:
- Inconsistent AI outputs across the team
- Duplicated effort in prompt engineering and context setup
- Knowledge silos where one person's AI knows things another's does not
- Difficulty onboarding new team members into AI-augmented workflows
## The context management hierarchy
TCM sits in the middle of a nested hierarchy:
- **Enterprise Context Management (ECM)**: organization-wide policies, compliance, standards
- **Team Context Management (TCM)**: team-level conventions and shared workflows
- **Project Context Management**: project-specific context
- **Personal Context Management (PCM)**: individual preferences, style, and personal knowledge
Context inheritance flows down: teams inherit enterprise standards and add their own. Projects inherit team standards. Individuals layer their personal context on top.
## Practical examples
- A shared CLAUDE.md in a Git repository that encodes coding conventions, architecture decisions, and team practices
- A team skill library that standardizes how AI handles code reviews, PR descriptions, or documentation
- Shared MCP server configurations for team-specific tools and services
- Team-level memory systems that capture decisions and their rationale