rollback-chain

Rollback analysis chains from RUNNING or WAITING to REJECTED state.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill rollback-chain-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rollback-chain
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/rollback-chain
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill rollback-chain-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rollback analysis chains to REJECTED state from RUNNING/WAITING, ensuring a controlled and auditable rollback.

Core Features & Use Cases

  • Orchestrates five rollback phases: main LLM, rollback-agent, validation, user confirmation, and README generation.
  • Validates artifacts, produces an audit-friendly report, and supports incident-response workflows.
  • Suitable for restoring a spec-driven workflow to a safe, rejected state after failures or escalations.

Quick Start

Run /rollback-chain 0001 to start the rollback.

Frequently Asked Questions about rollback-chain

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

FAQPage Schema
How do I rollback an analysis chain that is stuck in a RUNNING or WAITING state?

To rollback an analysis chain, you trigger a rollback command that transitions the chain from RUNNING or WAITING to a REJECTED state. This process applies across five orchestration phases, including artifact validation and user confirmation, ensuring the rollback is controlled and safe.

What is an analysis chain rollback and when do I need it?

An analysis chain rollback is a controlled process that moves a workflow to a REJECTED state after failures or escalations. You need it to restore a spec-driven workflow to a safe state, ensuring traceability and safety across all orchestration phases.

How does artifact validation work during a workflow rollback?

Artifact validation during a workflow rollback is orchestrated as one of five phases, ensuring that artifacts are checked before the chain reaches a REJECTED state. This phase guarantees that the rollback produces an audit-friendly report and maintains safety.

Can I use rollback orchestration for incident-response workflows?

Yes, you can use rollback orchestration for incident-response workflows. It safely restores a spec-driven workflow to a rejected state after failures or escalations, validating artifacts and producing an audit-friendly report to ensure full traceability.

What are the phases of a rollback orchestration?

The rollback orchestration consists of five phases: main LLM processing, rollback-agent execution, artifact validation, user confirmation, and README generation. These phases work together to ensure the analysis chain is safely moved to a REJECTED state with full audit logging.