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.