Replan on Failure

Name: Replan on Failure
Availability: InStock
Author: strategicmilk

Generate updated DAG plans after task failures or budget overruns.

Updated Mar 3, 2026

Search Tags:#orchestration #dag #task-scheduling #failure-recovery #budget-management #replan

Ready to run

npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill replan-on-failure

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Replan on Failure
Source: https://github.com/StrategicMilk/Vetinari-Orchestrastor/tree/main/vetinari/skills/catalog/foreman/replan-on-failure
Command: npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill replan-on-failure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When tasks fail, exceed budget, or scope changes, plans become invalid and pipelines stall. This skill evaluates the impact and generates a recovery plan to keep work progressing.

Core Features & Use Cases

Failure classification and impact analysis across the DAG.
Salvage assessment to preserve completed work and modify downstream tasks.
Budget recalculation and critical path recomputation.
Use Cases: Recover from worker failures, inspector rejections, budget overruns, or new requirements mid‑execution.

Quick Start

Instruct the foreman to replan the workflow after a task fails.

Frequently Asked Questions about Replan on Failure

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

FAQPage Schema

How do I recover a multi-agent orchestration workflow after a task failure stalls the pipeline?▼

To recover a multi-agent orchestration workflow after a task failure, generate an updated DAG plan that evaluates failure impact, preserves completed work, and modifies downstream dependencies to keep work progressing.

How does failure recovery handle budget overruns and token limits in a DAG task scheduling pipeline?▼

Failure recovery handles budget overruns by recalculating token and cost budgets and recomputing the critical path to ensure the revised DAG plan respects financial constraints while maintaining acyclicity.

What is the best way to preserve completed work when modifying downstream tasks after a worker failure?▼

The best way to preserve completed work after a worker failure is to perform a salvage assessment on the DAG, which identifies unaffected outputs and securely integrates them into the updated recovery plan.

Can I replan a task scheduling workflow when new requirements cause a scope change mid-execution?▼

Yes, you can replan a task scheduling workflow when new requirements cause a scope change mid-execution by generating a revised DAG plan that invalidates affected downstream dependencies and integrates the new parameters.

How do I trigger a replan after an inspector rejection in an automated orchestration pipeline?▼

To trigger a replan after an inspector rejection in an automated orchestration pipeline, instruct the foreman to remodel the workflow, which will classify the failure and generate an updated recovery plan.

Does replanning a failed DAG guarantee the updated plan maintains acyclicity across all downstream tasks?▼

Yes, replanning a failed DAG ensures the updated plan maintains acyclicity across all downstream tasks by validating the revised dependencies during the critical path recomputation phase.