agent-team-task-start

Mark a task as in_progress and record its current state_version.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool automates the transition of a work item from assigned to in_progress, ensuring the current state_version is captured for traceability.

Core Features & Use Cases

  • Start a task: transition the task state to in_progress and log the state_version for auditability.
  • Enforce ownership: verify the calling agent matches the task assignee before starting work.
  • State validation: ensure the task exists and is in a startable state before updating.

Quick Start

Run agent-team task start --task TASK_ID --agent AGENT to begin work on a task.

Frequently Asked Questions about agent-team-task-start

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

FAQPage Schema
How do I mark an agent task as in_progress and log its state version?

To start a task in an agent orchestration workflow, use the task start command to transition the task state to in_progress and log its current state_version for auditability.

Does task ownership enforcement prevent other agents from starting assigned work?

Yes, task ownership enforcement verifies that the calling agent matches the task assignee exactly before allowing the task to transition into the in_progress state.

What is the best way to ensure task state validation before starting active work?

The best way to ensure task state validation is to use a task start tool that verifies the task exists and is in a startable state before updating the record and state_version.

Why does task start fail if the work item is not in a startable state?

Task start fails because state validation requires the task to exist and be in a startable state before updating the record, ensuring proper orchestration workflow transitions and traceability.

Can I use this task start tool to enforce ownership across an orchestration workflow?

Yes, you can use this tool to enforce ownership and state tracking across the orchestration workflow by verifying the assigned agent and logging the state_version upon starting active work.