Teamharness Task Execution

Task Execution

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 or project result files.

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.

Task Directory

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

If a task spec asks you to write or submit shared/projects/..., report that boundary conflict to the Leader. Put Worker-owned deliverables under shared/tasks/{task-id}/...; the Leader owns project-level reports.

Acknowledge

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.

Execute

Keep all deliverables under the task directory. If you need private notes, use:

shared/tasks/{task-id}/workspace/

Use meaningful filenames for deliverables. Prefer names that describe the artifact's purpose, such as analysis.md, trace-summary.log, or patch-notes.md; avoid vague names like output.md when there are multiple files.

For report-style tasks whose expected output is shared/tasks/{task-id}/result.md, write the full report content to that file before calling submit_task. submit_task records structured status in task metadata and does not create or rewrite result.md.

If blocked, submit a BLOCKED result instead of silently waiting.

Submit

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:

• SUCCESS
• SUCCESS_WITH_NOTES
• REVISION_NEEDED
• BLOCKED

Submitting ends the task. Do not keep editing the old task after submission unless the Leader assigns a new task.

If you already wrote a detailed shared/tasks/{task-id}/result.md, include that path in deliverables; do not replace the report with only a short summary. Do not include shared/projects/... paths in deliverables.

When Matrix room context is available, submit_task automatically publishes shared/tasks/{task-id}/result.md and eligible deliverable files under the current task directory as Matrix m.file events. Check publishedArtifacts in the tool result for published, skipped, or failed artifact status. Do not upload task artifacts manually with message just to make them appear in the room file panel.

Completion Message

After submit_task returns ok: true, send a normal text message in the current Task room and mention the Leader with the exact Matrix user id or resolvable mention from the task spec:

@leader-user: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-user:matrix.local BLOCKED: demo-project-001-01 - <short blocker summary>