plan

Drafting a markdown plan without executing work is done by inspecting repository context in a read-only mode. This approach captures actionable strategies, recording goals, assumptions, and risks while preventing unintended file mutations or automated actions.

Creating a workflow strategy before automation involves isolating the planning stage to capture detailed deliverables. This method records goals, current context, key steps, and verification strategies into a markdown file for team review without risking premature edits.

Saving timestamped markdown plans requires writing output to a designated workspace-safe directory. The generated strategy files are stored with timestamped filenames, ensuring teammates can sequentially review and iterate on the recorded context and approaches.

Inspecting repository context to generate planning documents is possible under strict read-only restrictions. This allows the system to analyze existing files and strategy needs while explicitly forbidding any code edits, terminal mutations, or automated actions.

A planning workflow should include detailed deliverables such as goals, assumptions, approaches, affected files, tests, and risks. Recording these elements ensures clarity and comprehensive risk management before any actual execution work begins.

Automated workflows prematurely edit files when a planning mode is not enforced. Applying a plan-only approach isolates the strategy stage by capturing actionable steps in markdown, preventing noise and unintended changes before execution.