Team Manager

Team Manager

Intro

TeamMembers are the persistent participants in the project — humans, named AI personas, and services — that accumulate identity, personality, and tiered memory over time. This skill owns their lifecycle: creation, memory tree scaffolding, a curated international name pool, A2A-compatible Agent Cards, export/import bundles, and 10 consistency checks.

Unlike ephemeral worker invocations (role+seniority dispatches resolved on the fly and never persisted), TeamMembers live as directory trees on disk: persona.md + card.json + team-member.md (entity) + tiered memory subdirectories + optional private/ (gitignored).

MCP server. This skill ships a self-contained MCP server at mcp/server.py (PEP 723 script — requires uv and Python ≥ 3.10 on PATH). Agent harnesses reach its tools by reading a single MCP config file at startup, so the contents of mcp/mcp-config.json must be merged into the harness's MCP config and placed at the harness-specific path before this skill is usable.

ID convention

TeamMember IDs follow a single shape:

TEAMMEMBER-<slug>

where <slug> is the team-member's canonical kebab-case name (e.g. atlas, alice-chen, thrifty-otter). The slug starts with a letter and uses only [a-z0-9-]. It is also the directory name under context/team-members/<slug>/.

For type=ai-agent, the slug must be drawn from the team-manager name pool (see Name pool below). For type=human and type=service, any valid kebab-case slug is accepted.

TeamMember types

Do not promote every mention of a person into a TeamMember. And do not create a named AI persona for a one-off dispatch — use an ephemeral role+seniority invocation instead.

Memory tiers

Every team-member directory contains six tier subdirectories under context/team-members/<slug>/:

Plus private/ (optional, developer-local, gitignored) and three top-level files: persona.md (identity + personality prompt), card.json (A2A Agent Card), team-member.md (the entity itself).

Every memory file under a tier subdirectory must carry a frontmatter block validated against assets/memory-file-header.schema.json — required keys: tier, source, sensitivity, created.

Name pool & international naming policy

The name pool lives at data/name-pool.yaml (managed by this skill). It contains three gender-bucket lists (feminine, masculine, neutral) of international, short, human-friendly first names — ~60 total. Names from the pool are the canonical identifier source for AI personas.

Reservation lifecycle

• suggest_name(kind?) — pick a random available name, optionally filtered by gender bucket. Does not reserve.
• reserve_name(name, team_member_slug) — mark a name taken by a specific slug. Writes to data/name-pool.yaml atomically.
• release_name(name) — remove the reservation (e.g. on team-member deletion or re-export).
• list_available_names(kind?) — enumerate non-reserved names.

For create_team_member(type="ai-agent", ...), the slug must correspond to a name currently in the pool. The tool auto-reserves on success.

Consistency checks

check_consistency(slug) returns findings for a single team-member; check_all_consistency() aggregates across every team-member.

Each finding is {severity, code, team_member, path, message}. Codes:

Export / import

export_team_member(slug, output_path?) builds a tar.gz bundle at <slug>-export-<YYYY-MM-DD>.tar.gz containing:

• persona.md
• card.json (A2A Agent Card, conforms to assets/agent-card.schema.json)
• team-member.md (the entity)
• knowledge/, skills/, lessons/

Excludes journal/, relations/, private/ by default. During the memory-file walk, any file whose frontmatter declares sensitivity: confidential or sensitivity: pii is redacted (skipped).

import_team_member(tarball_path) extracts to a temp dir, validates the team-member.yaml against SCHEMA-team-member, validates card.json against the A2A Agent Card schema, and checks that a signature field is present on the card (crypto verification is deferred — signature field presence is a hand-off marker for future work). On success it copies the tree into context/team-members/<slug>/ and logs team_member.imported.

Deprecation note

This skill replaces actor-profile (DEC-20260422_0233-SpryTulip). The ACTOR-<slug> ID class and the create_actor/get_actor/etc. tools are deprecated in v0.19.0. A migration on context/actors/ runs in a separate phase; do not modify actor-profile from here.

Gotchas

• Creating a TeamMember for every mention. Reserved for persistent participants — the same rule as Actor. If they have no upcoming WorkItem/Binding/decision, don't promote them.
• Drawing an AI persona name outside the pool. team.name.off_pool will warn. Use suggest_name or list_available_names first.
• Putting confidential info outside private/. team.sensitivity.leak_risk catches it. The tier subdirectories are git-tracked; only private/ is safe for developer-local sensitive context.
• Hand-editing data/name-pool.yaml. Use reserve_name/ release_name — the tool preserves the document frontmatter and writes atomically.
• Forgetting init_memory_tree after create. create_team_member writes the entity but does not scaffold the tier subdirectories. Call init_memory_tree(slug) right after (or pass init_memory=True at create time, if implemented).
• Putting role+seniority dispatches here. Ephemeral worker invocations are NOT TeamMembers — they are resolved on the fly via task-router. Only persistent personas live in team-members/.