Menu
Trigger only when an observed failure, reproducible bug, regression, stack trace, failing test, or merge conflict requires evidence-based root-cause diagnosis before applying or recommending a fix.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | systematic-debugging |
| description | Trigger only when an observed failure, reproducible bug, regression, stack trace, failing test, or merge conflict requires evidence-based root-cause diagnosis before applying or recommending a fix. |
| requires | [] |
Use this skill only for a concrete failure signal:
Do not use this skill for general review, planned feature work, or post-implementation verification unless a failure must be diagnosed.
Record:
Run or reason through the reproduction path. If reproduction cannot be run, mark the blocker and continue only with explicit uncertainty.
Trace from failure signal to responsible code path:
Apply or propose a fix only after evidence supports the diagnosis. Keep changes scoped to the root cause.
Re-run the original reproduction and relevant regression checks. Report exact pass/fail evidence.
status: fixed | diagnosed | blocked | unresolved
symptom: string
reproduction:
attempted: boolean
commandOrSteps: string
result: passed | failed | blocked | not-run
evidence:
- source: string
detail: string
rootCause: string
fix:
applied: boolean
summary: string
filesChanged: string[]
verification:
attempted: boolean
commands: string[]
passed: boolean
failedChecks: string[]
blockedReason: string | null
nextAction: none | gather-more-evidence | apply-fix | ask-user | escalate
Trigger only when an already-approved PLAN.md or equivalent structured plan must be executed through wave-ordered tasks, isolated git worktrees, wave-level verification, final integration, and controlled merge handling; never create the plan or execute unapproved work.
Trigger only to inspect an existing diff, commit, branch, or PR for correctness, regression, security, performance, and maintainability issues; do not use to implement changes or run acceptance verification.
Trigger only when the user explicitly requests test-driven implementation or when an assigned task requires adding behavior by first writing a failing test, then minimal code, then refactoring without behavior change.
Trigger only when a coding task requires a written implementation plan before execution, especially multi-file or multi-step work needing dependency analysis, wave classification, and file-isolation-safe task partitioning; dispatches Planner to write a timestamped plan under ~/.yi-workflow/docs/plans/ and performs no implementation.
Trigger only after an implementation exists and must be validated against an explicit plan, acceptance criteria, or expected behavior by running relevant checks and reporting evidence-backed pass/fail results.