Task by Task · Free local practice
Build a source-grounded troubleshooting decision tree with AI
Authored local troubleshooting routes. This example runs locally; files selected here stay in browser memory.
Find the next useful correction
- File readable?
- Units and keys resolved?
- Known-answer case passes?
Each failure should lead to a focused input or method repair, not another vague request to try harder.
Take the technique to your next job
Build a troubleshooting decision tree from these approved rules only.
For each node, include the question, allowed action, source rule ID and
stop/escalation boundary. Preserve missing-source and failed-check paths.
Leave unsupported cases unresolved with a focused question.
Do not invent resets, external writes, integrations or account controls.
Provide editable source/file, readable path list and a few cases that
should expose a missing or incorrect branch.