Skip to content

AGENT_TEAMS.md

Latest commit

 

History

History
81 lines (59 loc) · 7.22 KB

AGENT_TEAMS.md

File metadata and controls

81 lines (59 loc) · 7.22 KB

Agent Teams — retort

Repo-local team mapping derived from .agentkit/spec/teams.yaml. Customize the Status, Primary Scope, Tech Stack, and Lead Agent columns for your repository. The orchestrator uses this file for task dispatch.

Overview

This document maps the canonical Retort team definitions (see UNIFIED_AGENT_TEAMS.md) to the concrete structure of this repository. Not all teams may be active — mark inactive teams so the orchestrator skips them during dispatch.

Team Roster

Team ID Focus Scope Accepts Handoff Chain Status Lead Agent
BACKEND backend API, services, core logic apps/api/**, services/**, src/server/**, controllers/** implement, review, plan testing → docs Active —
FRONTEND frontend UI, components, PWA apps/web/**, apps/marketing/**, src/client/**, components/** implement, review, plan testing → docs Active —
DATA data Database, models, migrations db/**, migrations/**, models/**, prisma/** implement, review, plan backend → testing Active —
INFRA infra IaC, cloud, Terraform/Bicep infra/**, terraform/**, bicep/**, pulumi/** implement, review, plan, investigate devops → security Active —
DEVOPS devops CI/CD, pipelines, automation .github/workflows/**, scripts/**, docker/**, **/Dockerfile* implement, review, plan testing → security Active —
TESTING testing Unit, E2E, integration tests **/*.test.*, **/*.spec.*, tests/**, e2e/**, playwright/** implement, review, test quality Active —
SECURITY security Auth, compliance, audit auth/**, security/**, middleware/auth* review, investigate — Active —
DOCUMENTATION docs Docs, ADRs, guides docs/**, docs/architecture/decisions/**, .github/**, README.md, CHANGELOG.md, CONTRIBUTING.md implement, review, document — Active —
PRODUCT product Features, PRDs, roadmap docs/product/**, docs/prd/** plan, review backend → frontend Active —
QUALITY quality Code review, refactoring, bugs, reliability, session retrospectives **/* review, investigate — Active —
TEAMFORGE forge Meta-team — creates, validates, and deploys new agent team specifications .agentkit/spec/**, docs/planning/agents-teams/**, docs/architecture/** plan, review, investigate, document quality → docs Active —
STRATEGIC OPS strategic-ops Cross-project coordination, framework governance, portfolio-level planning docs/planning/**, docs/architecture/**, .agentkit/spec/**, AGENT_BACKLOG.md, UNIFIED_AGENT_TEAMS.md, AGENT_TEAMS.md plan, review, investigate, document product → quality Active —
COST OPS cost-ops AI infrastructure cost reduction, vendor optimization, token efficiency docs/cost-ops/**, docs/planning/cost/**, config/models/**, config/pricing/** investigate, review, plan, document, implement infra → product → strategic-ops Active —

How to Customize

Activating / Deactivating a Team

  1. Change the Status column from Inactive to Active (or vice versa).
  2. Fill in the Primary Scope with actual directory paths in this repo.
  3. Set the Tech Stack to reflect the tools and frameworks used.
  4. Assign a Lead Agent identifier (used for mentions and escalation).
  5. Add any relevant notes about the team's role.

The orchestrator will skip inactive teams during /orchestrate dispatch.

Adding Custom Scope Patterns

Each team's scope patterns determine which files the orchestrator will assign to that team. Use glob patterns:

src/server/**       — all files under src/server/
src/api/*.ts        — TypeScript files directly in src/api/
tests/unit/server/* — server unit tests

Scope Overlap Resolution

When multiple teams have overlapping scope patterns, the orchestrator uses these priority rules:

  1. Most specific pattern wins. A deeper path match takes precedence.
  2. Explicit assignment overrides. A task explicitly assigned to a team via --teams flag takes precedence over pattern matching.
  3. Primary scope takes priority. The team whose scope lists the most specific matching directory owns the file.

Customize this file for your repository. User edits are preserved across syncs. Canonical team definitions: UNIFIED_AGENT_TEAMS.md