[FEATURE] Project-level Claude code plans directory

Preflight Checklist

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

Problem Statement

Claude Code does an excellent job of generating an execution plan based on a user’s prompt before implementing a task. However, the generated plans are currently stored at a global/system level, which creates friction in multi-project workflows.

Today, all plans are written to a shared location: /Users/$USER/.claude/plans

This causes several issues:

• Plans from different projects are mixed together, making them hard to associate with the correct codebase.
• It breaks project-level context, especially when working on multiple repositories simultaneously.
• Plans are not easily discoverable or reviewable within the project they belong to.
• It limits collaboration and version control possibilities for plans, since they live outside the project directory.

From a workflow perspective, plans are inherently project-specific artifacts, but they are currently treated as global/system artifacts.

Proposed Solution

Introduce support for project-scoped plan storage, so that Claude Code places generated plans within the project directory instead of the global system directory.

Desired Behavior

When a user invokes Claude Code within a project workspace and asks it to plan a task:

• The plan should be created and stored at the project level
• Each project maintains its own isolated set of plans

/Users/$USER/Projects/$PROJECT_DIR/.claude/plans

Optional Enhancements (nice-to-have)

• A CLI flag or config option to control plan scope (e.g. --plan-scope=project|global)
• Automatic detection of project root (similar to git root detection)
• Backward compatibility by falling back to global scope when no project context exists

This change would significantly improve clarity, scalability, and usability for developers working across multiple repositories, while aligning plan artifacts with the project they belong to.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_