plan

Generating a markdown plan from workspace context involves inspecting the read-only environment to produce a step-by-step document, which is then saved deterministically to .hermes/plans/ with a timestamped filename.

Yes, you can scope task planning and risk assessment without executing code by using a read-only context inspection mode that generates validation criteria and pre-execution steps without mutating the workspace.

Saving timestamped planning documents to .hermes/plans/ works by taking the generated markdown plan and writing it to the active workspace directory using a deterministic, timestamp-based filename for tracking.

No dependencies or components are required to create step-by-step plans in Hermes, as the planning mode operates independently to inspect context and generate validation criteria without external modules.

The best way to document pre-execution validation criteria for task planning is to generate a detailed markdown file that includes risk assessment and step-by-step actions before any code execution occurs.

You should use a dedicated plan mode instead of direct execution to ensure thorough risk assessment and validation criteria are established first, preventing unintended workspace mutations during task planning.