Plan files should use descriptive names instead of random generated names

Problem

When entering plan mode, Claude Code generates a random name for the plan file (e.g., majestic-swinging-fountain.md). These names are meaningless and make it hard to find or reference plans later.

Suggested improvement

Generate a descriptive, kebab-case name based on the task/problem being planned. For example:

• ping-timeout-during-deployment-analysis.md instead of majestic-swinging-fountain.md
• add-duration-config-option.md instead of elegant-dancing-river.md

The LLM already understands the task context when entering plan mode, so it should be straightforward to derive a meaningful name.

Current workaround

Users can ask Claude to rename the file after creation, or add a memory/feedback instruction to always use descriptive names. But this should be the default behavior.