root-cause plugins

by Melodic Software

Debug observed failures via a disciplined six-phase loop: build a fast deterministic reproduction signal, reproduce, rank falsifiable hypotheses, instrument, fix with a regression test, then clean up and post-mortem.

by Ravindra Kumar

Outcome-named autonomous fleets for the Orca runtime: each mission is one outcome with its own state machine and an evidence-backed definition of done. Missions compose best-of-breed worker recipes (mattpocock, gstack, addyosmani) over Orca — one router per worker. No vendor-named fleets. MIT.

by Scoutflo

Audit, harden, and monitor your infra and observability stacks (LGTM/VictoriaMetrics, ClickStack/ClickHouse/HyperDX, SigNoz, New Relic, Grafana, Sentry, PagerDuty, Datadog, ELK/Kibana, JSM Operations, Zenduty, groundcover, Prometheus (server + rule-engine plane), DigitalOcean, GCP, Azure/AKS, AWS) with scored reports, Slack briefs, and guided remediation. Runs entirely on your side with your credentials.

by dunnock

Create comprehensive Fishbone (Ishikawa/Cause-and-Effect) diagrams for structured root cause brainstorming. Guides teams through problem definition, category selection (6Ms, 8Ps, 4Ss, or custom), cause identification, sub-cause drilling, prioritization via multi-voting, and 5 Whys integration. Generates visual SVG diagrams and professional HTML reports. Use when brainstorming potential causes, conducting root cause analysis, facilitating quality improvement sessions, analyzing defects or failures, structuring team problem-solving, or when user mentions "fishbone", "Ishikawa", "cause and effect diagram", "6Ms", "cause analysis", or "brainstorming causes".

by dunnock

Conduct rigorous 5 Whys root cause analysis with guided questioning, quality scoring, and professional report generation. Use when performing root cause analysis, investigating problems, conducting 5 Whys sessions, troubleshooting recurring issues, or when user mentions "5 whys", "root cause", "why did this happen", "find the cause", or needs to identify underlying causes of defects, failures, or process problems. Includes validation tests, scoring rubric, and countermeasure development.

by Vivswan Shah

Never fix the same failure class twice. Climb every correction to the most durable response reachable: architecture and data structures first, then CI checks, then rules.

by Alexander Kurganov

Goldratt's Theory of Constraints Thinking Processes, applied to software systems and their architecture. The skill answers three questions in order. What to change: the Current Reality Tree. To what to change: the Evaporating Cloud, then the Future Reality Tree with negative-branch reservations. How to cause the change: the Prerequisite Tree, then the Transition Tree. Every link in a sufficiency tree is scrutinised with the Categories of Legitimate Reservation, and the user confirms the core problem before the cloud is built. The skill carries the procedure. The depth behind each tool and the categories sits in references beside it, each with its source. No script, no network, no credentials.

by Ibrohim Kholilul Islam

Blocks narrow fixes: forces a Hypothesis Ledger with a mandatory zoom-out hypothesis, 5 Whys with evidence gates, a systems lens, and information-gain gates before any bug fix, root-cause diagnosis, or plan is called done.

by Clock Lobster

A disciplined, four-gate bug-fixing methodology for coding agents: Concern (failing repro) -> Cause (root cause + siblings) -> Countermeasure (fix the architecture) -> Check (red-then-green proof + hardening). Reproduce-first, regression-proof, blast-radius-free fixes.

by scotscottmca

Bug-fixing agent crew for GitHub Copilot and Claude Code: an orchestrator that beams down mapper, investigator, basher and pr-writer.

by Carlos Araujo

Diagnostico diagnose-only: reproduz falhas, coleta evidencias, testa hipoteses e entrega relatorio de causa raiz sem executar correcoes.

by iyulab

Productivity toolkit for library maintainers - adaptive iterative development cycles, session handoff/resume and continuity-doc upkeep, conversational issue/PR triage, telemetry-driven issue discovery, and owner-manager backlog discovery that inspects what already exists (dependency currency, project configuration, docs and repo hygiene) while diagnosing, ranking, and staging new candidates with project philosophy alignment

by anhttq

Chưa biết dùng thì gõ /task-toolkit:help. Bộ toolkit lifecycle giao việc, tự chứa đầy đủ. Workspace tasks/{ID}/ theo 5 stage — 01-discovery · 02-plan · 03-backlog · 04-quality · 05-delivery — mỗi thư mục có README riêng nói chứa gì/ai ghi/đọc thứ tự nào. Pipeline: task-init → discovery (khi chưa có bản đồ kiến trúc) → task-survey (dependency walk) → analyze-spec (làm rõ input, grounded; Input Contract + Decision Log đóng câu hỏi khách chốt) → BUG: debug (chẩn đoán kỹ thuật, ra Immediate Cause có evidence + option fix, KHÔNG sửa code) → RCA 5-Whys → report → planning (kế hoạch fix) | FEATURE: planning (WBS + checklist tiến độ) → report BLUF 2 tầng VN/EN/JA → backlog-ticket (ticket chuẩn công ty + estimation). Kèm release-note: release note + deployment runbook cho CẢ LẦN RELEASE (auto 影響箇所マトリックス từ diff, đánh giá downtime, nháp deploy/smoke/rollback steps) — chạy như quy trình riêng, không nằm trong pipeline per-task. Mọi stage tái dùng artifact stage trước, không điều tra lại. Kèm HAI cổng kiểm độc lập trước khi gửi khách: report-reviewer (lập luận có vững) + verify-claims (mọi khẳng định kiểm được — số lượng, tên bảng/route, phiên bản, đường dẫn, lệnh, parity đa ngôn ngữ — đối chiếu nguồn khai báo/code/web, ra bảng Claim|Cách kiểm|Thực tế|Verdict; dùng được cả cho tài liệu mô tả hiện trạng). Export md/docx/pdf/xlsx. Generic mọi repo (framework autodetect, bản repo tự thắng).