Menu
Use when the user asks for a plan instead of executing work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when Hermes Agent needs X/Twitter search, public signal research, monitoring, or approval-gated account actions through the Hermes Tweet plugin.
Router Learning System — 越用越聰明嘅任務路由引擎。 每個 task 有最佳 path，Router 自動記錄經驗、動態調整、跳過爛 path。
Use when signaling work status across autonomous sessions.
Use when needing to standardize descriptions across many skill files at once — change format, fix wording, or enforce a convention like 'Use when...' prefix.
Use before making irreversible changes (deleting files, destructive git operations, large refactors). Use when you need the ability to roll back if something goes wrong. Use at the start of any task that modifies multiple files.
Use when the context window is getting full and tasks need breaking down.
| name | plan |
| description | Use when the user asks for a plan instead of executing work. |
| version | 1.0.0 |
| author | Hermes Agent |
| license | MIT |
| metadata | {"hermes":{"tags":["planning","plan-mode","implementation","workflow"],"platform":["cursor","codex","claude-code"],"related_skills":["writing-plans","subagent-driven-development"]}} |
| domain | agent-core |
| subdomain | planning |
| tokens | {"scan":180,"load":885,"category":"standard"} |
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.