agent-team-task-retry

Reset blocked, in_progress, or failed agent-team tasks to pending for retry.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams recover work that has stalled by moving tasks from blocked, in_progress, or failed back to a pending state so they can be retried.

Core Features & Use Cases

  • Reset task states to pending to reinitiate processing in agent-team workflows.
  • Clear retry-specific fields such as evidence, artifact, blocked_reason, and started_version to ensure a clean slate for the next attempt.
  • Record the reason for the retry in event logs to maintain traceability of decisions and outcomes.
  • Integrate with the agent-team CLI to automate error recovery in production workflows.

Quick Start

Run agent-team task retry --task TASK_ID --reason TEXT to reset a blocked, in_progress, or failed task to pending.

Frequently Asked Questions about agent-team-task-retry

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

FAQPage Schema
How do I retry a blocked or failed task in an agent-team workflow?

Reset blocked, in_progress, or failed tasks to pending by running the agent-team task retry command with the specific task ID and a reason. This clears previous execution metadata to ensure a clean slate for the next attempt.

What task states can be reset to pending for another attempt?

Tasks currently marked as blocked, in_progress, or failed can be validated and reset to pending. This state transition allows stalled work within the agent-team workflow to re-enter the processing queue for re-execution.

How do I clear retry metadata like blocked_reason when resetting a task?

Resetting a task to pending automatically clears retry-specific fields such as evidence, artifact, blocked_reason, and started_version. This ensures the task starts fresh without leftover data from the previous stalled execution attempt.

Does the agent-team task retry command require a reason for state transition?

Yes, the agent-team task retry command requires a reason argument to record the retry rationale in event logs. This maintains traceability of decisions and outcomes for workflow error recovery.

Do I need the agent-team binary to reset failed workflow tasks?

Yes, the agent-team binary is required to reset failed workflow tasks. The skill integrates directly with the agent-team CLI to automate error recovery and validate allowed source states during the task retry process.