Results for “failure-classification”

Enumerating failure modes via pre-mortem analysis. Systematically identifies failure scenarios for plans, designs, and features, scoring them with RPN/AP. Does not write code.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

Autonomously repairs failed task verification by choosing retry, decompose, prune, or escalate strategies before surfacing to the user.

>-

当需要在多个领域积累独特竞争优势，避免单一技能风险时

Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".

Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".

当遭遇挫折、失败或结果不如预期时，用于将负面经验转化为成长燃料

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.

Structured workflow to reproduce, diagnose, plan, fix, verify, and record a bug fix, requiring a deterministic reproduction before diagnosis and minimal changes only.

Reproduces failures, gathers evidence, tests hypotheses, fixes root causes, and adds regression coverage.

Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".

Repairs failed task verification by choosing a strategy: retry with adjustments, decompose into sub-tasks, prune infeasible tasks, or escalate to the user.

Conduct failure mode and effects analyses. TRIGGERS - Use when user needs help with fmea-guide related tasks.

Graceful degradation when primary approach fails. Try alternates in priority order; record which path succeeded for future routing.

跨 TypeScript、Python、Go 的健壮错误处理模式——涵盖类型化错误、错误边界、重试策略及优雅降级

Reproduce a bug as a failing regression test, fix until green, review, and commit via a delegated pipeline.

Use to quantify what support quality failures cost — rework, credits, escalation handling, complaints and churn — with the causal limits stated. Trigger for "what do our quality failures cost", "cost of rework in support", "business case for improving quality", "how much is bad support costing us", or a quality investment that needs a number attached.

PASS/FAIL eval rubrics and alignment loops for Sid Orchestra. Use when the user says sid evals, @sid-evals, grade this, eval gate, alignment score, or wants to stop AI slop with evaluation gates.

Investigate and fix bugs, crashes, null references, and runtime errors in QuizVerse.

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

Conduct failure mode and effects analyses. TRIGGERS - Use when user needs help with fmea-guide related tasks.

Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".

Imported skill errors from agentskills

Root-cause analysis with hypothesis tracking. Trigger: 'debug', 'broken', 'not working', 'fix this bug', /debug

Imbalance is not itself a problem — it is a symptom that the default loss and the

Failure diagnosis, DAG mutation, and escalation engine for the WinDAGs meta-DAG. Receives failure information and quality vectors from the Evaluator. Classifies failures on four dimensions. Follows a five-level escalation ladder. Applies seven mutation types with saga compensation. Enforces BC-EXEC-002, BC-EXEC-003, BC-FAIL-002, BC-FAIL-005. Activate when operating as the Mutator role in the meta-DAG, when diagnosing node failures, when restructuring a DAG at runtime, or when deciding escalation level.