[FEATURE] Allow descriptive/custom plan file naming instead of random adjective-noun combinations

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

Plan files are currently named with random adjective-noun combinations (e.g., lively-bubbling-umbrella.md). This makes it difficult to:

• Identify what a plan was about without opening it
• Manage multiple plans across sessions
• Keep the ~/.claude/plans directory organized over time

Current Behavior

Plans are saved to ~/.claude/plans/ (or custom plansDirectory) with auto-generated names like:

• lively-bubbling-umbrella.md
• quiet-dancing-river.md

Proposed Solution

Proposed Solution

Allow Claude to generate descriptive filenames based on the task context. Options:

1. Auto-descriptive naming (preferred): Derive filename from the task/conversation context

• fts-search-refactoring.md
• auth-flow-implementation.md

1. User-specified naming: Allow users to specify a plan name via flag or prompt

• /plan --name "fts-refactor"

1. Hybrid: Auto-generate descriptive name, allow override

Additional Considerations

• Collision handling: append timestamp or short hash if name exists
• Setting to toggle between current random naming and descriptive naming for users who prefer the current behavior
• Filename sanitization for special characters

Use Cases

• Reviewing past plans for similar tasks
• Auditing what was planned vs implemented
• Team collaboration where plans are committed to repo
• Cleaning up old plans selectively without opening each file

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_