Repeated State Detection and Escalation

What problem does it solve?

Repeated-state detection helps pipelines avoid endless retry loops by recognizing when the same blocker signature occurs across consecutive revisions and escalating to human review.

Core Features & Use Cases

• Exact-match fingerprinting of blocker state to detect repetition across revisions.
• Durable persistence of signature data and a holding-state flow to prevent regression into previous stages.
• Escalation artifacts (e.g., lead-review.md) and lightweight handoffs to guide external review after repeats.
• Use Case: In an editorial pipeline, when a blocker reoccurs after two revisions, automatically escalate to lead-review while keeping the article in a holding state.

Quick Start

Use the repeated-state-detection skill to escalate when the same blocker signature appears in consecutive revisions.