「root cause」の検索結果

Use when a task needs the judgment of an Electromechanical Equipment Assembler — verifying shaft/coupling alignment directly rather than trusting an initial functional test that only confirms the device runs, applying fastener torque to spec with a calibrated tool rather than by feel, routing wire to account for the equipment's full range of motion rather than its static assembled position, or distinguishing electrical from mechanical root cause when a device malfunctions.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Compliance Officer — deciding whether a suspected violation triggers a mandatory regulatory filing or disclosure, designing or risk-rating a compliance monitoring program, running a violation investigation to root cause, briefing a board/audit committee on compliance findings, or responding to a regulatory exam finding.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Bookkeeping, Accounting, and Auditing Clerk — reconciling a bank or credit card account, resolving an AP three-way-match discrepancy before payment, coding an expense to the correct account and department, tracing a general ledger discrepancy to root cause, or running a month-end close checklist.

日本語の概要は準備中です。原文の説明を表示しています。

Audit financial reconciliation workflows -- evaluate automated transaction matching engines, intercompany balance reconciliation, suspense and clearing account health, variance root-cause investigation, and close calendar integration.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze an incident response program for playbook coverage, MTTR optimization opportunities, evidence collection readiness, root cause analysis quality, and post-incident review effectiveness. Triggers: building a SOC, assessing IR maturity, optimizing detection-to-recovery timelines.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze a workplace safety incident tracking system for incident classification accuracy, root cause analysis depth, OSHA 300 log recordkeeping compliance, trend analysis capabilities, and leading indicator identification..

日本語の概要は準備中です。原文の説明を表示しています。

Analyze franchise inventory management for par level optimization, waste tracking and root cause analysis, and theoretical vs. actual usage variance.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze manufacturing defect detection and quality control systems — computer vision inspection pipelines, SPC control charts, Six Sigma process capability (Cp/Cpk), defect classification taxonomies, root cause analysis tooling, and measurement system analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Capture learnings from a campaign, launch, sprint, or initiative using Five Whys (Taiichi Ohno, Toyota Production System) for root cause analysis and Start-Stop-Continue for action planning. Append reusable insights to knowledge/learnings.md so future runs of the OS get smarter. Use when the user asks for a retro, retrospective, post-mortem, "what did we learn", "campaign wrap-up", "lessons learned", or after a campaign or launch ends. Critical feedback loop that makes the OS compound over time. For the numbers review itself, see kpi-review. For planning the next campaign, see campaign-brief.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze budget vs. actual variances, identify root causes, and recommend corrective actions. Use when an accountant or finance professional says "explain this variance", "budget vs. actual analysis", "why did we miss budget", "favorable / unfavorable variance", "price volume variance", "management reporting commentary", "explain the P&L variance to the CFO", "what drove the cost overrun", "revenue shortfall analysis", or needs to write the narrative behind a financial result. Also trigger when someone shares a table of actuals vs. budget and needs to explain the gaps - even if they don't use the word "variance".

日本語の概要は準備中です。原文の説明を表示しています。

**WORKFLOW SKILL** — Register and generalize agent errors into reusable lessons. USE FOR: when the user corrects the agent, capturing what went wrong, analyzing root cause, generalizing the error into a lesson that prevents recurrence. Use to register errors, analyze mistakes, create lessons, generalize corrections. DO NOT USE FOR: general debugging, writing tests, code review.

日本語の概要は準備中です。原文の説明を表示しています。

Root cause debugging before fixes. Use when investigating bugs, diagnosing test failures, troubleshooting unexpected behavior, or when previous fix attempts failed. Enforces investigate-first discipline.

日本語の概要は準備中です。原文の説明を表示しています。

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.

日本語の概要は準備中です。原文の説明を表示しています。

MUST USE for any real runtime debugging across ANY language or binary — crashes, silent failures, wrong responses, stuck processes, memory leaks, async misbehavior, unexplained timing, reverse engineering. Runs a hypothesis-driven loop: form ≥3 hypotheses, investigate in parallel, after 2 failed rounds spawn Oracles from orthogonal angles, confirm root cause, lock with a failing test, fix minimally, QA by actually USING the system, scrub artifacts. The actual HOW lives in `references/` — READ THEM. Triggers: 'debug this', 'why is X not working', 'hanging', 'attach a debugger', 'reverse engineer', 'pwndbg', 'gdb', 'lldb', 'node inspect', 'tsx debug', 'pdb', 'dlv', 'delve', 'rust-gdb', 'set a breakpoint', 'context window exploded', 'why is the response empty', 'attach the debugger', 'debug it', 'why is this happening', 'trace this bug', 'reproduce and fix', 'silent failure', 'HTTP 200 but empty', 'why did it stop', 'inspect the binary', 'reverse engineering', 'playwright'.

日本語の概要は準備中です。原文の説明を表示しています。

Enter explore mode for technical work — a thinking partner for {{engine_name}} code, architecture, and implementation decisions before you write any code. Use it to investigate a technical solution, design the architecture of a feature, choose between frameworks or libraries, compare implementation approaches, analyze how existing code or a system works, or deeply root-cause a complex bug without fixing it yet. The ultra mode adds adaptive artifacts (a C4 view, ADRs, a dependency graph) to the research folder — run it on "ultra research", "ultra explore" or "ultraresearch"; otherwise run the default. Trigger on "let's explore this technical solution", "how should we architect this feature", "which framework should we use", "run an ultra research on the save system", "investigate this error deeply". Research and analysis only — it never writes code. This is the CODE / engineering explorer — for GAME-DESIGN, GDD, mechanics, or balance research (no code) use /unikit-gd-explore.

日本語の概要は準備中です。原文の説明を表示しています。

Bug-fixing workflow that coordinates diagnosis, test-driven reproduction, root-cause analysis, and targeted fixes. Use when the user wants to fix a bug with thorough investigation and regression testing.

日本語の概要は準備中です。原文の説明を表示しています。

Review failing CI checks on pull requests, diagnose root causes, and fix issues. Covers common failures: tests, linting, type checks, security scans, and builds.

日本語の概要は準備中です。原文の説明を表示しています。

Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose Azure application and infrastructure issues with a structured, evidence-based workflow. Use this skill when users ask to troubleshoot outages, latency, failures, configuration drift, or anomalies. Root cause analysis using logs, metrics, traces, and dependency mapping.

日本語の概要は準備中です。原文の説明を表示しています。

Relentless delivery mode for complex, multi-step tasks. Use when: multi-file features, unclear root cause debugging, multi-angle research, architecture decisions with trade-offs. Activates parallel subagent dispatch and strict verification.

日本語の概要は準備中です。原文の説明を表示しています。

Trace failing signals through the RTL hierarchy, classify root cause, and write a debug report per issue — no fix is proposed

日本語の概要は準備中です。原文の説明を表示しています。

Own goal-first engineering outcomes: investigate, find root cause, design, plan, then delegate implementation unit-by-unit to cursor-implementation-loop, this plugin's kernel skill, with verification and honest reporting. Use to fix, build, or own an outcome end to end; investigate-and-fix; "make X work"; or plan-then-execute in one request. A request with an approved plan or equivalently precise spec that needs nothing beyond implementation belongs directly to cursor-implementation-loop. Requires this plugin's cursor-implementation-loop skill; they ship together.

日本語の概要は準備中です。原文の説明を表示しています。

Own goal-first engineering outcomes: investigate, find root cause, design, plan, then delegate implementation unit-by-unit to implementation-loop with verification and honest reporting. Use to fix, build, or own an outcome end to end; investigate-and-fix; "make X work"; or plan-then-execute in one request. A request with an approved plan or equivalently precise spec that needs nothing beyond implementation belongs directly to implementation-loop. Requires implementation-loop and an authenticated backend CLI to execute.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose and repair a failed GEODE smoke workflow within the requested acceptance criteria. Preserve failed evidence, verify the shared root cause, and apply merge, rebuild, or live rerun stages only when authorized.

日本語の概要は準備中です。原文の説明を表示しています。