Plan mode exit is ambiguous. Unclear whether approving implementation or a docs-only change

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

When Claude is in plan mode, ExitPlanMode is used for two very differentsituations:

1. "I've planned code changes — approve so I can implement them"
2. "I've planned a docs/spec edit only — approve so I can write one file"

The approval dialog looks identical in both cases, making it hard to know what you're actually authorising.

Proposed Solution

2 Suggestions:

• Two exit tools: ApprovePlanForImplementation vs ApprovePlanForDocumentEdit — gives the UI a signal to show different confirmation language
• ExitPlanMode metadata: Add an optional parameter like actionType: "code" | "docs-only" | "mixed" and a filesAffected list so the UI can render "Claude wants to edit 1 markdown file" vs "Claude wants to write code across 3 files"

Alternative Solutions

_No response_

Priority

Inconvenience

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_