plan

const (
	ToolNameEnterPlanMode = "enter_plan_mode"
	ToolNameExitPlanMode  = "exit_plan_mode"
	ToolNameSubmitPlan    = "submit_plan"
)

const (
	SearchHintEnterPlanMode = "switch to plan mode to design an approach before coding"
	SearchHintExitPlanMode  = "leave plan mode once the user has approved the plan"
	SearchHintSubmitPlan    = "submit the implementation plan for user review and approval"
)

const (
	DescriptionEnterPlanMode = "" /* 346-byte string literal not displayed */
	DescriptionExitPlanMode  = "" /* 177-byte string literal not displayed */
	DescriptionSubmitPlan    = "" /* 307-byte string literal not displayed */
)

const EnterPlanModePrompt = `Plan mode is a read-only mode: while it is on you cannot change files, only read, investigate and design.

If the user explicitly asks you to enter plan mode, or to design or investigate without changing anything, call ` + "`enter_plan_mode`" + `.

You do NOT need plan mode to propose a plan. To put a plan in front of the user for review and approval, call ` + "`submit_plan`" + ` directly: it works in any mode, execute included.

## Enter plan mode on your own only when

You want the read-only guard while you design. This mode exists to obtain the user's
alignment, not to organise work. Enter it when a choice belongs to the user and settling
that choice before any file is touched costs less than settling it after:

- Several defensible designs exist and the user has not indicated which one they want
- The work is hard to undo or expensive to redo: data migrations, auth or permission
  changes, deletions, a published interface or schema
- The acceptance criteria themselves are ambiguous, so you cannot tell what "done" looks
  like from the repository

Investigating a wide, unfamiliar or multi-file area is NOT a reason on its own. Reading
is free in either mode, and a tracked task list carries the roadmap while you read, so a
request that is merely large and unambiguous belongs in execute mode.

## Do NOT enter plan mode when

- The task is a small, obvious, bounded fix
- The user already gave you explicit step-by-step instructions
- The request is pure research or reading with no planned implementation
- You already have enough context to start immediately and the risk is low
- The task is multi-step but unambiguous and the approach is not in question:
  open a tracked task list with ` + "`task_create`" + ` and execute it directly. A
  task list is not a plan, it needs no approval, and entering this mode just to
  be able to track the steps costs a full round of alignment for nothing.

## What to do in plan mode

1. Explore the relevant code using read-only tools (` + "`read_file`" + `, ` + "`glob`" + `, ` + "`grep`" + `, and ` + "`bash`" + ` for ls/cat/git log/find)
2. Clarify ambiguous requirements with ask_user_question if needed
3. Design a concrete, ordered implementation plan
4. Call ` + "`submit_plan`" + ` with the full plan content and a short slug
5. Wait for the user to review — they may send feedback (revise and resubmit) or approve
6. On approval, follow the approval message: implement directly if plan mode was
   already exited for you, or call ` + "`exit_plan_mode`" + ` if you are still in plan
   mode, then track the work with ` + "`task_create`" + ` / ` + "`task_update`" + `

DO NOT edit or create source files while in plan mode.
The plan is presented to the user as an interactive artifact for review and approval.`

const ExitPlanModePrompt = `` /* 994-byte string literal not displayed */

const SubmitPlanPrompt = `` /* 2250-byte string literal not displayed */