failure-analysis

Classify failures and extract root causes into a structured failure_analysis artifact.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Burburton/amazing-specialists --skill failure-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: failure-analysis
Source: https://github.com/Burburton/amazing-specialists/tree/main/.opencode/skills/common/failure-analysis
Command: npx skills add https://github.com/Burburton/amazing-specialists --skill failure-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Failure analysis provides a disciplined approach to transform failure data from tests, reviews, and verifications into actionable insights, ensuring root causes, impact, and next actions are clearly captured for remediation and learning.

Core Features & Use Cases

  • Structured failure_type classification (TEST_FAILURE, REVIEW_REJECTION, VERIFICATION_FAILURE, ENVIRONMENT_ISSUE, REQUIREMENT_ISSUE) with severity and description.
  • Root-cause extraction with contributing factors and a boolean is_systematic indicator.
  • Output artifacts including fix_requirements, retry_assessment, impact_analysis, and recommended next steps to guide engineers and automation.
  • Seamless integration with auto-report workflows and knowledge bases for continuous improvement.
  • Typical scenarios: after a failed test, after a review rejection, after a verification failure, or after repeated reworks to assess project health and escalation needs.

Quick Start

Run failure-analysis on a failed task to generate a complete, actionable failure_analysis artifact.

Frequently Asked Questions about failure-analysis

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

FAQPage Schema
How do I extract root causes from failed test logs and CI-CD pipeline errors?

Failure analysis processes failure logs, task context, and previous attempts to extract root causes and contributing factors. It classifies the failure type, assesses impact severity, and produces fix requirements with retry plans for faster remediation.

What is the best way to classify and document verification failures and review rejections?

Structured failure classification categorizes verification failures and review rejections by type, severity, and description. It captures root causes, impact assessments, and recommended next steps into a reusable artifact for continuous improvement.

Can I automate failure analysis and integrate it with my existing quality assurance workflows?

Yes, failure analysis integrates with auto-report workflows and knowledge bases. It consumes failure logs and task context to produce structured artifacts containing retry assessments and escalation recommendations for automated quality assurance pipelines.

How do I assess whether repeated test failures require escalation or a retry plan?

Retry assessment evaluates previous attempts and task context to determine if a failure is systematic. It generates an escalation workflow recommendation and a retry plan, indicating when repeated reworks require higher-level intervention.

Does this approach handle environment issues and requirement issues, or just test failures?

Failure analysis handles environment issues and requirement issues alongside test failures, review rejections, and verification failures. It applies root cause extraction and impact assessment across all these scenarios to deliver comprehensive remediation guidance.