What to write before moving a coding problem to another AI tool

Before moving a coding problem to another AI tool, write a transfer note with the goal, current failure, environment, files involved, rejected fixes, and the exact help needed next.

Moving tools without a note often restarts the investigation. The new tool does not know which package version was already checked, which command failed, which branch of the hypothesis tree is dead, or which constraint is non-negotiable. The user then spends time correcting basic suggestions instead of moving forward.

A good transfer note is short and factual. Start with the target behavior. Add the command or user action that fails. Include the exact error or wrong output. Name the environment, runtime, and files involved. Then list the fixes already tried and what happened. End with the next request: find root cause, review patch, suggest a test, compare two designs, or explain a confusing API response.

Do not paste secrets, full customer data, private local paths, or the whole project. Replace private values with shapes. The point is to carry reasoning state, not expose everything.

The best sign that the note is ready is that another person could read it and avoid the first three obvious questions.

What to write before moving a coding problem to another AI tool

// COMMENTS

ON THIS PAGE