Add 'Yes, using Claude command [name]' option to plan mode for custom workflow integration
Problem
Current plan mode only offers binary Yes/No options when presenting execution plans. This creates workflow friction for users who prefer to execute plans using custom Claude commands rather than the default execution method.
Proposed Solution
Add a third option to plan mode: 'Yes, using Claude command [command-name]' that allows users to execute the validated plan using their preferred custom Claude command.
Use Case
Many users develop custom Claude commands (such as /work-on, /implement, /systematic-approach, etc.) that provide structured, methodical approaches to task execution. These users currently must:
- Review the plan in plan mode
- Select 'No' to decline default execution
- Manually invoke their preferred command (e.g., '/work-on [task description]')
This breaks the flow and duplicates effort since the plan validation step becomes disconnected from the execution step.
Benefits
- Maintains Plan Validation: Users still get the benefit of reviewing and approving plans before execution
- Workflow Integration: Seamlessly integrates with users' custom development methodologies
- Reduced Friction: Eliminates the No → custom command workaround pattern
- Flexibility: Accommodates different development styles and project-specific workflows
- User Experience: Streamlines transition from planning to systematic execution
Example Implementation
Plan mode could:
- Detect available Claude commands in the user's setup
- Offer them as execution options alongside Yes/No
- Pass the plan context to the selected command for systematic execution
Example User Flow
Instead of:
Enable:
Target Users
- Project-based developers who prefer systematic workflows
- Users with established custom Claude command patterns
- Teams that have standardized on specific development methodologies
- Anyone who finds value in both plan validation AND structured execution
This enhancement would provide significant value for users who rely on custom Claude commands for consistent, high-quality development workflows while maintaining the safety and clarity benefits of plan mode.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗