Feature Request: Configurable Plan File Storage Path & Plan Templates

Problem Statement

Currently, Claude Code stores plan files in ~/.claude/plans/ (user-level directory). This makes it difficult to:

1. Version control plans alongside project code
2. Share plans with team members via git
3. Reference past plans for specific projects
4. Standardize plan formats across a team

Proposed Solution

Option 1: Configurable Plan Path

Add a setting in .claude/settings.json to specify plan storage location:

{
  "planPath": ".claude/plans/"
}

Option 2: Auto-detect Project Plans Directory

Automatically use .claude/plans/ if it exists in the project root, falling back to ~/.claude/plans/ otherwise (similar to how .claude/commands/ works for project-scoped commands).

Additional Feature: Plan Templates

Support a template file (.claude/plan-template.md) that Claude uses as a starting structure when creating new plans. This would help teams standardize plan documentation formats.

Use Cases

• Teams wanting to track planning decisions in version control
• Projects requiring consistent plan documentation formats
• Developers working on multiple projects who want project-specific plan history
• Code review workflows where plans need to be visible to reviewers

Current Workaround

Currently requires manual copying of plan files from ~/.claude/plans/ to the project directory after plan mode exits.

Consistency with Existing Features

This would be consistent with how other Claude Code features work:

• Commands: .claude/commands/ (project) vs ~/.claude/commands/ (user)
• Skills: .claude/skills/ (project-scoped)
• Settings: .claude/settings.json (project) vs ~/.claude/settings.json (user)

Plans should follow the same pattern for consistency.

---

Thank you for considering this enhancement!