Preflight Checklist

• I have searched existing requests and this feature hasn't been requested yet
• This is a single feature request (not multiple features)

Problem Statement

I have established a discipline around using plan files:

• I place them in a plans/ directory in my repo
• I name them PLAN-xxxx-some-description.md
• I leave them around and refer to them by name in future prompts even after completion: "In PLAN-XYZU we did this in a certain way, lets do it again that way"
• I have workspace directions around this discipline: "If you are working on a plan, REMEMBER which plan during compaction summarization and re-read the plan afterward", "Plans are places in plans/PLAN-xxxx-some-thing.md", etc.
• I keep them checked in and can refer to how they've changed over time
• I can review and iterate them before actually implementing them
• I often work with these plan files in plan mode to keep Claude Code focused

This has worked very well for me, and I often work with plans in plan mode this way.

The new plans feature places plans in a hidden my home directory with meaningless names, it also places them outside the repo where I am doing work, and plan mode now seems confused when I refer to "plan files" in planning mode, thinking I am referencing the home directory location.

Proposed Solution

I think the new planning mode would be perfect if, instead of writing the plan to a random location, we could give it a location and name pattern in the repo .claude/settings.json (or could just be moved there). Making meaningful, non-colliding names is a very easy task for Haiku, so I think implementing this could be done cheaply in terms of token budget. This would allow very easy tracking, editing, and long-term reference to plan files as well.

Alternative Solutions

I will probably experiment with renaming my files to "designs", but I am still somewhat bothered by the placement of plans in the ~/.claude location - this is not a convenient place to edit or review files that I'm managing as part of a workspace or development flow.

It is still very informative to see the contents of this file within my workspace under any circumstance, and the placement in ~/.claude in such a disorganized way is very inconvenient.

If the plans directory has been made in this way with some sincere design conviction, it would also be helpful to just have documentation of what the intended practice is around plan file editing and management. Is this meant to feed into a UI or editing flow an a way that I don't understand?

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

No response

Additional Context

No response