plan

Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes/plans/` directory, and do not execute the work.

High Quality

New

Join 0+ developers using this skill

skill

Software Development

intermediate

0 installs

4/5 quality

View Source

Last updated: April 23, 2026

AI Skill Market Insights

Real data. Real impact.

Popularity

Rising

Emerging

Active Users

Developers

Quick Start

Install Command

mkdir -p ~/.hermes/skills/software-development/plan && curl -o ~/.hermes/skills/software-development/plan/SKILL.md https://raw.githubusercontent.com/NousResearch/hermes-agent/main/skills/software-development/plan/SKILL.md

TEAR & SHARE

3-5hrs/WK

RISING

0.0K+ USING

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 inside the active workspace under
```
.hermes/plans/
```
.

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

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

.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.

plan

AI Skill Market Insights

Quick Start

Install Command

TEAR & SHARE

Tags

writing-plans

Be Part of the 0+ Developer Community

Plan Mode

Core behavior

Output requirements

Save location

Interaction style

License

requesting-code-review

subagent-driven-development

systematic-debugging

test-driven-development

Channels

Learn

Compare

Company