plan

To generate a Markdown project plan without executing code, use a non-executive planning mode that converts intent into actionable steps. It creates a concrete plan and saves it directly to your workspace, ensuring a safe planning phase before any mutations occur.

Creating actionable execution plans for software development tasks is best handled by generating a detailed, step-by-step Markdown document. This approach provides a safe, non-executive way to outline workflows and eliminate guesswork before any actual code execution begins.

Yes, you can save operational workflow plans directly to your active workspace. The plan is saved as a timestamped Markdown file under a dedicated plans directory, ensuring your project management documents are organized and accessible for future reference.

Planning mode does not execute mutations or external actions on your files. It strictly generates a concrete, actionable Markdown plan for the active workspace, providing a safe environment to review steps before committing to any code execution or file modifications.

You need to write a Markdown plan for research planning when you require an explicit, actionable strategy before starting your task. This non-executive approach converts intent into a concrete document, eliminating guesswork and outlining clear steps for operational workflows.