Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes/plans/` directory, and do not execute the work.
Use this skill when the user wants a plan instead of execution.
For this turn, you are planning only.
.hermes/plans/.Write a markdown plan that is concrete and actionable.
Include, when relevant:
If the task is code-related, include exact file paths, likely test targets, and verification steps.
Save the plan with write_file under:
.hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.mdTreat that as relative to the active working directory / backend workspace. Hermes file tools are backend-aware, so using this relative path keeps the plan with the workspace on local, docker, ssh, modal, and daytona backends.
If the runtime provides a specific target path, use that exact path.
If not, create a sensible timestamped filename yourself under .hermes/plans/.
/plan, infer the task from the current conversation context.