Feature Request: Meaningful plan file names

Feature Request: Meaningful Plan File Names

Summary

Use descriptive kebab-case names for plan files instead of random adjective-verb-noun patterns.

Current Behavior

Plan files are saved with random names:

• fuzzy-snuggling-fog.md
• abundant-noodling-firefly.md
• bubbly-launching-mango.md

Proposed Behavior

Name plans with a short kebab-case summary of the feature/task:

• add-user-authentication.md
• fix-cache-invalidation.md
• refactor-api-endpoints.md

Why This Matters

1. Findability: When returning to a project, it's hard to find the relevant plan among dozens of randomly-named files
2. Context: The filename itself provides context about what the plan covers
3. Consistency: Aligns with how specs and other project documents are typically named
4. History: Makes ~/.claude/plans/ a useful reference of past work