Plan

Skill ChrisLamDev/hermes-core-skills/skills/plan

25 executable AI agent skills for debugging, planning, token efficiency, and security

Install

npx -y skills add ChrisLamDev/hermes-core-skills --skill plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user asks for a plan instead of executing work.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, as published. Nobody here has run it

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.