rollback-chain

Name: rollback-chain
Availability: InStock
Author: oogdz

Roll back analysis chains from RUNNING/WAITING to REJECTED via 5-phase orchestration.

Updated Apr 2, 2026

Search Tags:#workflow #rollback #validation #orchestration #artifact #SSOT #analysis-chain

Ready to run

npx skills add https://github.com/oogDZ/2 --skill rollback-chain

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rollback-chain
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/rollback-chain
Command: npx skills add https://github.com/oogDZ/2 --skill rollback-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rolling back an analysis chain when problems are discovered, ensuring a safe, auditable transition from RUNNING/WAITING to REJECTED with predefined phases, artifact checks, reporting, and user confirmation.

Core Features & Use Cases

5-phase orchestration: main LLM → rollback-agent → validation → AskUserQuestion → REJECTED + README.
Artifact validation and comprehensive reporting to preserve an auditable trail.
Prompt-driven user confirmation step to finalize rollback.

Quick Start

Run /rollback-chain <NNNN> to initiate a rollback of the analysis chain from RUNNING/WAITING to REJECTED following the 5-phase orchestration.

Frequently Asked Questions about rollback-chain

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

FAQPage Schema

How do I safely roll back a running analysis chain to a rejected state?▼

Rolling back a running analysis chain requires a structured 5-phase orchestration that transitions the workflow from RUNNING or WAITING to REJECTED through artifact validation, reporting, and user confirmation.

What is the process for ensuring an auditable rollback of an orchestration workflow?▼

An auditable rollback of an orchestration workflow enforces a fixed SSOT-based rollback flow that validates artifacts, generates comprehensive reports, and produces a README artifact for full traceability.

How do I initiate a rollback for a specific analysis chain instance?▼

You initiate a rollback for a specific analysis chain instance by running the rollback command with the target chain identifier, triggering the main LLM and rollback-agent phases for structured execution.

Does the rollback flow require manual confirmation before rejecting a workflow?▼

Yes, the rollback flow requires a prompt-driven user confirmation step to finalize the transition to REJECTED, ensuring safe and deliberate orchestration control over the analysis chain.

When should I use a structured rollback orchestration instead of manually stopping a workflow?▼

You should use a structured rollback orchestration when you need to preserve an auditable trail, as it enforces a fixed SSOT-based flow with artifact validation and README traceability rather than a simple halt.