plan-modelisted

# Plan Mode ## When to Activate This skill is enabled when the user explicitly requests to enter "Plan mode" or enters `/prompts:plan` / `/plan`. Treat the task description given by the user as `$ARGUMENTS` (if the user directly enters `/prompts:plan <description>`, then `<description>` will be `$ARGUMENTS`). Goal: Develop a implementable and traceable technical execution plan for the task description `$ARGUMENTS` in the current working directory, and save the plan to the `plan/` directory of this project. - User explicitly says `/plan`, `/prompts:plan`, or "enter Plan mode". - User wants a structured execution plan written under `plan/`. - User asks for planning before implementation and does not want code changes yet. > Note: This skill only takes effect when the user explicitly triggers Plan mode and does not affect normal conversations. > In actual use, you can pass: > > - Enter `/` and select `/prompts:plan` in the pop-up window; or > - Configure shortcut keys in the terminal and automatically enter `/prompts:plan` to obtain a one-click experience similar to "/plan". ## When to Activate - The user explicitly asks for Plan mode, `/prompts:plan`, `/plan`, or a plan file under `plan/`. - The task should be decomposed before implementation instead of executed directly. - A previous plan needs a deliberate update or replacement with traceable scope. ## Red Flags - The task is treated as executable while non-goals, decision boundaries, or lane ownership are unknown. -