task:adjuster

Analyzes task failures, detects stagnation, and applies adaptive upgrade strategies.

4|2|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/lazygophers/ccplugin --skill task-adjuster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task:adjuster
Source: https://github.com/lazygophers/ccplugin/tree/main/plugins/tools/task/skills/adjuster
Command: npx skills add https://github.com/lazygophers/ccplugin --skill task-adjuster

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps recover from task failures by analyzing the root cause, detecting repetitive issues, and applying appropriate escalation strategies to get back on track.

Core Features & Use Cases

  • Failure Analysis: Identifies the reason for a task failure.
  • Stagnation Detection: Detects if the same error is repeating.
  • Adaptive Strategies: Implements escalating strategies like retrying, debugging, replanning, or asking for user input.
  • Use Case: When a coding task fails repeatedly, this Skill can analyze the error, suggest retrying with a minor adjustment, or if the problem persists, escalate to debugging or replanning the task.

Quick Start

Use the adjuster skill to analyze the failure and determine the next best action.

Frequently Asked Questions about task:adjuster

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

FAQPage Schema
How do I recover from repeated task failures during workflow automation?

Task failure analysis identifies the root cause of errors during workflow automation. It examines loop command step failures and repetitive errors to determine why a task fails, enabling targeted recovery actions rather than blind retries.

How do I detect error stagnation when the same task failure keeps repeating?

To detect error stagnation when the same task failure repeats, this Skill monitors task execution for repetitive errors. Recognizing repeated failures stops unproductive retry loops and triggers progressive failure escalation strategies for effective task recovery.

What is the best way to apply failure escalation strategy in a coding loop?

The best way to apply failure escalation in a coding loop is to use adaptive strategies that progressively shift from retrying with adjustments to debugging, replanning, or requesting user input. This matches the intervention level to the persistence of the error.

When should I escalate a repetitive error to replanning instead of retrying?

You should escalate to replanning when repetitive error detection confirms stagnation and minor retry adjustments fail. If root cause analysis indicates the fundamental approach is flawed, escalating to replanning provides a more viable task recovery path.

Can I use task adjustment reporting to trace root causes for loop command step failures?

Yes, actionable adjustment reporting traces root causes for loop command step failures. The report details the failure analysis and the chosen escalation strategy, providing clear documentation for why a specific recovery action was applied.