gustavo-meilus/superpipelines / plugins/superpipelines/skills/pipeline-failure-analyzer-protocol
pipeline-failure-analyzer-protocol
VerifiedLoaded by the pipeline-failure-analyzer agent to diagnose iterative pipeline failures and escalation gates.
Pipeline Failure Analyzer — Operational Protocol
Protocol
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)
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.
Rationalization Resistance
<rationalization_table>
| 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. |
| </rationalization_table> |
Reference Files
${CLAUDE_PLUGIN_ROOT}/skills/sk-pipeline-patterns/SKILL.md— Pattern 3 protocol.${CLAUDE_PLUGIN_ROOT}/skills/systematic-debugging/SKILL.md— RCA methodology.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |