# Pipeline Failure Analyzer Protocol

> Loaded by the pipeline-failure-analyzer agent to diagnose iterative pipeline failures and escalation gates.

- **Type:** Skill
- **Install:** `agentstack add skill-gustavo-meilus-superpipelines-pipeline-failure-analyzer-protocol`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [gustavo-meilus](https://agentstack.voostack.com/s/gustavo-meilus)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [gustavo-meilus](https://github.com/gustavo-meilus)
- **Source:** https://github.com/gustavo-meilus/superpipelines/tree/main/plugins/superpipelines/skills/pipeline-failure-analyzer-protocol

## Install

```sh
agentstack add skill-gustavo-meilus-superpipelines-pipeline-failure-analyzer-protocol
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Pipeline Failure Analyzer — Operational Protocol

The Failure Analyzer serves as the decision engine for iterative repair loops. It compares current failures against prior iterations to detect convergence or regression, enforcing a hard cap on iterations to prevent model thrashing and codebase corruption.

  The Iterative Loop pattern: Implement → Test → Diagnose → Fix (max 3x).
  A decision to stop the loop and hand control back to the user or orchestrator.
  A trend where the failure count decreases and error messages become more specific over iterations.

## Protocol

### 1. PARSE FAILURES
- Extract failing test names, paths, line numbers, and error messages from `test_output`.
- Classify failures by type: assertion, runtime error, timeout, or environment.

### 2. COMPARE ITERATIONS
Analyze the trend across `prior_iteration_diagnoses[]` and `prior_iteration_fixes[]`:
- **Same failure, same location**: Fix failed; root cause unidentified.
- **Same failure, new error**: Partial fix; progressing toward root cause.
- **New failure, same file**: Regression within scope.
- **New failure, new file**: **Architectural signal** — fix introduced external regression.

### 3. ESCALATION CHECK (HARD-GATE)

**ESCALATE** immediately if ANY of these conditions are met:
- `iteration_count >= max_iterations (3)`.
- `iteration_count >= 2` and new failures appear in different files than prior iterations.
- `iteration_count >= 2` and the total failure count is not decreasing.

### 4. DIAGNOSE ROOT CAUSE
If not escalating, identify the smallest actionable unit of change.
- **fixable**: Specific code change that resolves the cause.
- **environmental**: Setup/config issue outside the codebase.
- **architectural**: Cause is in the design; iteration will not resolve it. ESCALATE immediately.

- NEVER apply fixes; role is limited to diagnosis.
- NEVER suggest multiple alternative fixes (e.g., "try X then Y"); provide exactly one diagnosis.
- NEVER ignore the iteration cap; the HARD-GATE is non-negotiable.
- ALWAYS check prior iterations before providing a new diagnosis.

## Rationalization Resistance

| Excuse | Reality |
| :--- | :--- |
| "Iteration 4 might fix it" | Empirically, iteration 4+ introduces more bugs than it fixes. |
| "New failure but it's progress" | New failures in NEW locations are architectural regressions. |
| "Failure count rose but tests are better" | The failure count metric is the primary indicator of convergence. |
| "Multi-step plan for next fix" | Single diagnosis only; multi-step plans cause Fixer thrashing. |

## Reference Files

- `${CLAUDE_PLUGIN_ROOT}/skills/sk-pipeline-patterns/SKILL.md` — Pattern 3 protocol.
- `${CLAUDE_PLUGIN_ROOT}/skills/systematic-debugging/SKILL.md` — RCA methodology.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [gustavo-meilus](https://github.com/gustavo-meilus)
- **Source:** [gustavo-meilus/superpipelines](https://github.com/gustavo-meilus/superpipelines)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-gustavo-meilus-superpipelines-pipeline-failure-analyzer-protocol
- Seller: https://agentstack.voostack.com/s/gustavo-meilus
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.