Fix It

Goal

Turn a diagnosis into a decision-complete implementation plan that another agent or engineer can execute confidently. Bridge between diagnosis (troubleshoot-app / diagnose-bug) and code work.

Use lightweight BDD / contracts as the repair oracle (handbook/concepts/13-quality-trace.md). State what should happen, where that expectation lives, whether to use/refine/create it, and how tests/evals prove it. Prefer existing DocSlime REQUIREMENTS/TESTING, issue BDD, schemas, and tests over inventing a parallel definition.

Name the quality regime for evidence (handbook/concepts/11-quality-regimes.md): A = contracts/golden tests; B = journeys/a11y/data-plane; C = traces/evals (hand agent/LLM product bugs to agents + Langfuse when the failure is generative). Debt labels name interest — they do not demote the pain (12-bugs-and-debt.md).

When NOT to use

• Pure structure cleanup with no behavior change → refactor-it
• “Add tests only” with no repair → test-it
• No failing contract yet / exploring options → research-it or recon issue
• Runaway agent thrash → agents slap first

Required Input