teamharness-task-execution

Executes assigned tasks in shared task directories and submits structured results via taskflow.

5.5k|677|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill teamharness-task-execution
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: teamharness-task-execution
Source: https://github.com/agentscope-ai/HiClaw/tree/main/plugins/teamharness/skills/team/task-execution
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill teamharness-task-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Workers in a multi-agent team need a consistent protocol for acknowledging assigned tasks, keeping deliverables in the right shared directories, and reporting completion or blockers back to the Leader without corrupting project-level state.

Core Features & Use Cases

  • Task Acknowledgment: Claims assigned tasks with the taskflow ack_task action and reads the task spec before starting work.
  • Scoped Deliverables: Keeps all Worker-owned files under shared/tasks/{task-id}/workspace, progress, and result.md while protecting Leader-owned project files from edits.
  • Structured Submission: Submits results with taskflow submit_task using SUCCESS, SUCCESS_WITH_NOTES, REVISION_NEEDED, or BLOCKED statuses, and publishes deliverables as Matrix room file events.
  • Use Case: A Worker agent receives TASK_ASSIGNED in a Matrix room, acknowledges the task, writes an analysis report to the task directory, submits it with deliverables listed, and posts a TASK_COMPLETED message mentioning the Leader.

Quick Start

Acknowledge the task assigned to you with taskflow ack_task, read the spec in shared/tasks/{task-id}/spec.md, write your deliverables in the task workspace, then submit with taskflow submit_task and notify the Leader in the room.

Frequently Asked Questions about teamharness-task-execution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute an assigned task as a Worker agent?▼

Acknowledge the task with the taskflow ack_task action, read shared/tasks/{task-id}/spec.md, write deliverables under the task workspace, then call submit_task with a status and deliverables list. Finish by posting a TASK_COMPLETED message mentioning the Leader in the room.

How do I submit task results with taskflow submit_task?▼

Call submit_task with the taskId, a status of SUCCESS, SUCCESS_WITH_NOTES, REVISION_NEEDED, or BLOCKED, a summary, and a deliverables array of file paths under the task directory. Submission ends the task, so do not keep editing afterward.

Which files can a Worker edit in the shared task directory?▼

A Worker owns shared/tasks/{task-id}/workspace, progress, and result.md. The Leader owns meta.json, spec.md, and all shared/projects/ files, so Workers must not edit those and should report any spec that asks them to.

What should I do when a task is blocked?▼

Submit a BLOCKED result through submit_task instead of silently waiting, then send a message in the Task room mentioning the Leader with a short blocker summary. Ask focused questions rather than inventing missing task files.

When should I not use the taskflow task execution workflow?▼

Do not use it for readiness checks, direct questions, or explicit requests to reply with specific text. Answer those directly in the current room instead of acknowledging or submitting a task.