Homework

When saving the plan, I always tell Claude where to save it: under ~/.claude/plans. Sometimes it renames it to the issue name; sometimes it just gives it a funny name. Just telling Claude to save the plan is enough ? Instead of specifying where?

@Geronimo Orozco, just saying “save the plan” isn’t enough for predictable results, but the workflow actually points somewhere other than a local file.

Have a look at the Plan phase in the GitHub Feature Workflow lesson. Under “After the plan is ready” it suggests asking Claude to post the plan as a comment on the GitHub issue instead of saving it to disk. That sidesteps the naming problem entirely, since the issue number is an address you already have.

It also fits how the rest of the workflow is built. Each phase runs in a new session with clean context, so the plan needs to live somewhere the next session can reach with one reference. “The plan is on issue #12” works. “It’s in a file under ~/.claude/plans with a name Claude picked” doesn’t.

If you’d still like local copies, be explicit about the filename rather than just the directory:

Save the plan to ~/.claude/plans/issue-12-note-storage.md

When you leave the filename open, Claude picks one, and nothing makes that choice consistent between runs. That’s the variation you’re seeing. Worth knowing as well that ~/.claude/plans is global rather than per project, so plans from different repos all collect in the same folder.

Hope that helps 🙂