plan

Generating a markdown plan without executing code involves creating a written document that captures context, goals, assumptions, and steps. This ensures project files remain non-mutated while providing a clear, actionable planning output for later reference.

Plan mode in task management workflows is a process that helps teams avoid premature execution by generating a clear, actionable plan. It inspects context, delineates steps, and saves a written plan instead of directly executing work on project files.

To save a timestamped markdown plan, you write the document and store it using a specific filename pattern like YYYY-MM-DD_HHMMSS-plan.md. The plan is automatically saved to the active workspace's designated .hermes/plans/ directory for later reference.

No, planning mode enforces non-mutating behavior and ensures no code is executed during context inspection. Delivery is purely planning output, meaning your project files remain completely untouched while generating the actionable plan.

The best way to structure a task management plan in markdown is to include context, goals, assumptions, approach, and steps. This concise structure provides a comprehensive, ready-to-save document that guides execution without premature action.