[FEATURE] Configurable plan file location

[nkoji21]

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

In Plan mode, .md files are created in the ‎.claude directory by default.
This makes plans less visible in day‑to‑day development and separated from broader project documentation.

Proposed Solution

Allow configuring where plan files are created, preferably the project root, or a custom path.
This could be controlled via ‎.claude/settings.json.

{
  "planFileLocation": "root"
}

When using a custom path:

{
  "planFileLocation": "custom",
  "planFileCustomPath": "docs/plans"
}

Alternative Solutions

• Manually moving plan files after creation (easy to forget).
• Symlinks from root to ‎.claude (platform‑dependent).
• Editor tasks/scripts to copy files (maintenance overhead).

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

• Keep plans visible at the project root alongside README and other docs.
• Store planning artifacts with the rest of technical documentation to improve discoverability.
• Standardize plan locations across repos via a shared settings file.

Additional Context

• Validate ‎planFileCustomPath (repo‑relative vs absolute).
• Document precedence when both fields exist; require custom path only when location is ‎"custom".
• Ensure backward compatibility: if absent, default to ‎.claude.

[github-actions]

Found 3 possible duplicate issues:

1. [FEATURE] Add planStorage setting to configure plans directory location #12939
2. [FEATURE] Project-specific plan storage location #13180
3. [Feature Request] Plan mode should support plan files outside ~/.claude/plans directory #12707

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[nkoji21]

Totally agree this overlaps with past requests about making the plans directory configurable.
The key difference in my proposal is adding a granular, project‑level setting via .claude/settings.json so teams can standardize plan location per repo without global overrides.

Concretely, I’m proposing a settings schema that supports both “root” and a validated custom path:

{
    "planFileLocation": "root"
}

and, for custom paths:

{
    "planFileLocation": "custom",
    "planFileCustomPath": "docs/plans"
}

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[cjbhaines]

I would find this feature really useful as well. I like to commit the plans as part of the work because they can be useful to refer the agent back to when resuming work on a feature that hasn't been touched for a while.

At the moment, I'm stuck with the only option of copying the plan into the repo from the .claude directory once the work is finished, which is tedious.

This is exactly the path I use as well: "docs/plans"

[keyvanm]

Seconded