القائمة
Use when a TeamHarness Worker or remote member receives an assigned task, acknowledges it, executes it, submits a result, or reports blockers.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work.
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.
| name | teamharness-task-execution |
| description | Use when a TeamHarness Worker or remote member receives an assigned task, acknowledges it, executes it, submits a result, or reports blockers. |
Use this skill when executing assigned work as a Worker or remote member.
Claim only tasks assigned to you. Read the task spec, keep deliverables in the task directory, ask focused blocker questions, and submit a structured result.
Do not change project-level state unless the task spec explicitly authorizes it.
Do not use this skill or taskflow for readiness checks, direct questions, or explicit requests to reply with specific text. Answer those directly in the current room.
Your assigned task lives under:
shared/tasks/{task-id}/
The Leader owns:
shared/tasks/{task-id}/meta.json
shared/tasks/{task-id}/spec.md
You own:
shared/tasks/{task-id}/workspace/
shared/tasks/{task-id}/progress/
shared/tasks/{task-id}/result.md
Do not edit:
shared/projects/{project-id}/meta.json
shared/projects/{project-id}/plan.md
shared/projects/{project-id}/result.md
unless the task spec explicitly tells you to.
When you are mentioned with TASK_ASSIGNED, first pull or inspect the task
directory if needed, then acknowledge with taskflow:
{
"role": "worker",
"action": "ack_task",
"payload": {
"taskId": "demo-project-001-01"
}
}
If ack_task fails because the task is missing or assigned elsewhere, stop and
report the blocker to the Leader in the current room. Do not invent task files.
Read:
shared/tasks/{task-id}/spec.md
before doing the work.
Keep all deliverables under the task directory. If you need private notes, use:
shared/tasks/{task-id}/workspace/
If blocked, submit a BLOCKED result instead of silently waiting.
Submit with taskflow:
{
"role": "worker",
"action": "submit_task",
"payload": {
"taskId": "demo-project-001-01",
"status": "SUCCESS",
"summary": "Completed the assigned work.",
"deliverables": [
"shared/tasks/demo-project-001-01/workspace/output.md"
]
}
}
Use one of:
SUCCESSSUCCESS_WITH_NOTESREVISION_NEEDEDBLOCKEDSubmitting ends the task. Do not keep editing the old task after submission unless the Leader assigns a new task.
After submit_task returns ok: true, send a normal text message in the
current assignment room and mention the Leader:
@leader:matrix.local TASK_COMPLETED: demo-project-001-01 - Result: shared/tasks/demo-project-001-01/result.md
If the task spec gives an exact completion line, preserve that line exactly and
include one short summary sentence. A tool call, tool-output thread, or
result.md file does not count as the completion message. Do not use
NO_REPLY after successful submission.
For blockers:
@leader:matrix.local BLOCKED: demo-project-001-01 - <short blocker summary>