Menu
Use to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
| name | teamharness-organization |
| description | Use to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work. |
Use this skill to reason about team roles and responsibility boundaries.
Leader owns planning, delegation, acceptance, and requester reporting. Workers own assigned task execution. Remote members participate as invited local agents or humans. Manager owns control-plane operations.
Do not let a Worker silently become project owner. Do not let a remote member act like a controller-managed Worker unless the team explicitly models that role.
Leader owns:
Worker owns:
shared/tasks/{task-id}/spec.mdshared/tasks/{task-id}/result.mdRemote member owns only the work explicitly assigned to that member. Treat remote members as participants, not controller-managed runtime resources.
Manager owns control-plane operations such as creating workers, changing model configuration, deploying teams, and managing runtime state. TeamHarness skills must not instruct agents to call control-plane APIs.
Never write secrets, credentials, tokens, authorization headers, or live runtime
state into TEAMS.md, project files, task specs, task results, or Matrix
messages. If a task needs credentialed access, refer only to the approved
credential name or environment variable name, not its value.
Discover and call MCP Server tools via the mcporter CLI. Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs. Includes workflow for generating skill documentation for new MCP servers.
Use when TEAMS.md Communication Contract needs detailed routing: Channel / Room Selection Protocol, Requester Report Delivery Protocol, or Message Tool Protocol. It resolves current session vs Team Room vs assignment room vs requester reply_route vs external channel, and explains when to use the message MCP tool. Do not use it to choose Quick Task or Project Work, create rooms, delegate tasks, check results, or accept project state.
Use for TeamHarness shared workspace paths, explicit filesync operations, and shared project/task artifact boundaries.
Use only after Project Work mode is selected, before TeamHarness projectflow calls, project DAG or Loop planning, ready-node resolution, iteration recording, project files, result acceptance, or project progress updates.
Use only after Project Work mode is selected, when a TeamHarness Leader delegates ready project nodes, writes task specs, checks Worker results, and routes completion or blocker messages.
Use when a TeamHarness Worker or remote member receives an assigned task, acknowledges it, executes it, submits a result, or reports blockers.