mirrors/hermes-agent
1
0
Fork 0
mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-04-25 00:51:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
hermes-agent/skills/software-development/plan/SKILL.md
Developer 967cec4331 fix(skill): use profile-isolated path for plan storage 
Plan skill was writing to .hermes/plans/ relative to the backend
workspace, causing all profiles to share the same plans directory.

Now writes to ~/.hermes/plans/ which is expanded against the
subprocess HOME ({HERMES_HOME}/home/), ensuring each profile has
its own isolated plans directory.

Fixes #12533.
2026-04-19 21:50:05 +08:00

2 KiB
Raw Blame History

name description version author license metadata
plan Plan mode for Hermes — inspect context, write a markdown plan into the profile's plans directory, and do not execute the work. 1.0.0 Hermes Agent MIT
hermes
tags related_skills
planning
plan-mode
implementation
workflow
writing-plans
subagent-driven-development

Plan Mode

Use this skill when the user wants a plan instead of execution.

Core behavior

For this turn, you are planning only.

  • Do not implement code.
  • Do not edit project files except the plan markdown file.
  • Do not run mutating terminal commands, commit, push, or perform external actions.
  • You may inspect the repo or other context with read-only commands/tools when needed.
  • Your deliverable is a markdown plan saved under the profile's ~/.hermes/plans/ directory.

Output requirements

Write a markdown plan that is concrete and actionable.

Include, when relevant:

  • Goal
  • Current context / assumptions
  • Proposed approach
  • Step-by-step plan
  • Files likely to change
  • Tests / validation
  • Risks, tradeoffs, and open questions

If the task is code-related, include exact file paths, likely test targets, and verification steps.

Save location

Save the plan with write_file under:

  • ~/.hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md

This path is expanded against the subprocess HOME ({HERMES_HOME}/home/), ensuring each profile has its own isolated plans directory. Falls back to os.path.expanduser() when the subprocess home directory does not exist.

If the runtime provides a specific target path, use that exact path. If not, create a sensible timestamped filename yourself under ~/.hermes/plans/.

Interaction style

  • If the request is clear enough, write the plan directly.
  • If no explicit instruction accompanies /plan, infer the task from the current conversation context.
  • If it is genuinely underspecified, ask a brief clarifying question instead of guessing.
  • After saving the plan, reply briefly with what you planned and the saved path.