plan

To generate a Markdown planning document without executing commands, use a deterministic planning workflow that outlines goals, steps, and validation criteria, saving the blueprint to your workspace.

The best way to outline project steps without mutating source files is to generate a concrete plan document that defines validation criteria and goals, ensuring a clear blueprint before any action.

A planning assistant saves generated workflow plans by creating a Markdown file with a timestamped filename, storing the document in the active workspace for later review or execution.

Yes, you can create a development plan for any task context without running code changes, as the planning process generates a readable document and does not perform source file mutations.

The limitation of plan-only mode is that it generates a document without performing changes to source files or running commands, meaning you must execute the outlined steps separately.

Yes, you need an active workspace directory to save generated Markdown plan files, as the deterministic workflow stores the timestamped output document in the workspace path.