plan

A non-executing markdown plan is generated by inspecting the current workspace context and saving a timestamped file to the .hermes/plans/ directory. It documents goals, approach, steps, risks, and validation while strictly preventing code execution or file mutations.

Yes, you can generate task decomposition steps without workspace modifications. This Skill enforces read-only context inspection to derive goals and writes the resulting workflow design strictly to the .hermes/plans/ directory, ensuring no unintended file mutations occur.

The best way to document project goals and risks before code execution is using a dedicated planning mode that generates a markdown file. It captures the current context, outlines the approach, details the steps, highlights risks, and defines validation criteria safely.

Yes, this planning mode supports workflow design for complex task decomposition. It analyzes the active workspace to break down tasks into actionable steps, documenting the approach, risks, and validation methods in a timestamped markdown file without executing any code.

You should use a non-executing plan to prevent unintended changes and save time during software planning. By enforcing read-only context inspection, it safely documents your approach, steps, and risks in markdown before any code execution or file mutations are allowed.

The main limitation of generating markdown plans is that no code execution or file mutations are allowed outside the .hermes/plans/ directory. It enforces read-only context inspection, meaning it strictly drafts documentation rather than implementing the planned software changes.