agent-team-task-complete

Mark assigned tasks done with evidence and artifact paths.

2|Updated May 10, 2026
One-click install
npx skills add https://github.com/tae2089/agent-team --skill agent-team-task-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-team-task-complete
Source: https://github.com/tae2089/agent-team/tree/main/skills/agent-team-task-complete
Command: npx skills add https://github.com/tae2089/agent-team --skill agent-team-task-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to finalize tasks by recording concrete evidence and an artifact path, ensuring verifiable completion.

Core Features & Use Cases

  • Mark a task as done with evidence and a run-scoped artifact path.
  • Validate the task assignee and coordinate sync checks within agent-team workflows.
  • Support optional force to bypass sync conflicts after explicit approval from the orchestrator.

Quick Start

Complete the assigned task by passing the required task_id, agent, evidence, and artifact path.

Frequently Asked Questions about agent-team-task-complete

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

FAQPage Schema
How do I mark an agent-team task as complete with evidence?

To complete an agent-team task, you finalize it by submitting the task_id, agent, evidence, and a run-scoped artifact path. This records concrete evidence ensuring verifiable task completion across agents.

What inputs are required to finalize task completion in an agent-team workflow?

Finalizing task completion requires four inputs: task_id, agent, evidence, and artifact. The skill validates that the agent matches the original assignee before marking the task as done.

Can I bypass sync conflicts when completing an agent-team task?

Yes, you can bypass sync conflicts using the --force option. This requires explicit approval from the orchestrator to finalize the task and override any synchronization issues within the agent-team workflow.

Why does task completion require an artifact path?

Task completion requires an artifact path to ensure verifiable evidence and associated artifacts are captured. This run-scoped path provides concrete proof that the assigned task was successfully executed.

What happens if the agent submitting the task evidence does not match the assignee?

The skill validates the agent against the assignee before allowing task completion. If they do not match, the task cannot be finalized unless the sync conflict is explicitly bypassed with orchestrator approval.