user-guided-debugging

name	user-guided-debugging
description	Use when the user explicitly asks to debug, repair, or refactor one issue at a time with visible problem statements before each edit and a next-issue prompt after each scoped fix.

User-Guided Debugging

Tool Commands

Use the command packet before applying this skill's workflow:

python3 tools/agent_tools/skill_tool_commands.py show --skill user-guided-debugging --format text

Execute the required and task-matching conditional commands that the packet prints.

1. Read agents/skills/user-guided-debugging.md.
2. Select exactly one next target issue.
3. If implementation repair is in scope, prepare a fresh work-capable subagent worker for that target issue before handoff; use the task-appropriate implementation agent from .codex/agents/*.toml.
   • Prefer spark_worker only when eligible; otherwise use worker.
   • Pass the visible problem statement, scoped repair surface, forbidden drift, and validation route to that worker.
4. Before editing, show the user:
   • target object or path
   • concrete problem
   • evidence or failing code path
   • intended repair surface
5. Do not patch before that problem statement is visible in chat.
6. Keep the patch scoped to the displayed target unless evidence moves the root cause; if it moves, show the new problem statement before editing.
7. Do not run tests, smoke runs, lint, docs checks, benchmarks, or other validation commands in this cadence unless the user explicitly asks for that execution after the patch.
8. If the user explicitly asks for validation after the patch and validation fails, show failing_contract, observation_level, cause_classification, intent_preservation, and evidence before the next edit. Use intent_preservation for the same-intent repair or escalation route. Do not simplify to pass, revert, delete intended behavior/tests, weaken an oracle, or downscope validation without that five-field classification.
9. Report the patch result, state that validation was not run when it was skipped, and present the next concrete issue.
10. Use this skill only when the user explicitly asks for this cadence; do not make it an agent-orchestration default.