Keep the AI plan.md file with your code changes

Some AI coding tools create a plan.md file before they start making changes. That file is often worth keeping.

The problem is that the plan file usually lives inside the AI tool's own profile or session folder. That means it is easy to lose, not backed up with the repository, and not version-controlled with the actual code changes.

In practice, the file can be useful documentation. It often shows what the tool planned to change, in which order, and why. The commit diff shows what changed. The plan file can help explain the intent behind the change.

A simple fix is to copy the file into your repository before the session disappears.

copy "~\.copilot\session-state\54a5ed90-2243-43c8-a02c-3351c9ceb6cf\plan.md" C:\Code\MyApp\Documentation

You can then review the file and commit it together with the code if it adds useful context. A folder like Documentation or docs is usually enough.

This is especially handy when you want to understand later what was done and why, or when another developer needs the reasoning behind the change and not just the final diff.

One small note: review the file before committing it. It may contain temporary notes, rough ideas, or local paths that you do not want to keep as-is.

So the practical tip is simple: if your AI tool creates a plan.md, do not leave it in a private session folder. Copy it somewhere safe, and commit it when it helps document the work.

Hope this helps!