Use this skill when the user wants a plan instead of execution.
For this turn, you are planning only.
Write a markdown plan that is concrete and actionable.
If the task is code-related, include exact file paths, likely test targets, and verification steps.
Treat 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
.