---
name: omk-troubleshooting
description: Systematic troubleshooting for build failures, test failures, environment issues, dependency conflicts, and agent workflow blockers.
---

## Steps

1. Capture exact error message and stack trace.
2. Identify the smallest reproducible scope.
3. Check environment, versions, and dependencies.
4. Search for known issues in project memory and docs.
5. Apply minimal fix.
6. Verify fix with the failing command.
7. Document the root cause in `.omk/memory/risks.md` if persistent.
