Plan — Write a markdown plan to .hermes/plans/; no execution
Plan — Write a markdown plan to .hermes/plans/; no execution
Start with meaning, then move to detail.
This lesson explains Plan — Write a markdown plan to .hermes/plans/; no execution as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Core behavior, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Plan — Write a markdown plan to .hermes/plans/; no execution without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Write a markdown plan to .hermes/plans/; no execution
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Core behavior
Read this after the foundation, then connect it to the previous step.
- 04Output requirements
Read this after the foundation, then connect it to the previous step.
- 05Save location
Read this after the foundation, then connect it to the previous step.
- 06Interaction style
Read this after the foundation, then connect it to the previous step.
- 07Overview
Read this after the foundation, then connect it to the previous step.
- 08When a Full Implementation Plan Helps
Read this after the foundation, then connect it to the previous step.
- 09Bite-Sized Task Granularity
Read this after the foundation, then connect it to the previous step.
- 10Task 1: Build authentication system
Finish here to verify the result and special cases.
Copy only after you understand the effect.
**Right size:**## Plan Document Structure
### Header (Required)
Every plan MUST start with:### Task Structure
Each task follows this format:Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.