[omh] Hermes Plan workflow: structured planning before execution.
SkillScore82Maintained
Automatic
◆Project Management pack
Last verified 8/19/2026
What it changes
Passed 18 of 22 test cases with the skill, and 9 of 22 without it.
Without skill41%
With skill82%
Checks it passed that the model alone missed
The output explicitly names assumptions alongside goals and non-goals.
The output recommends ultrawork single-owner persistence for the task.
The response includes explicit non-goals for the ORM migration project.
and 10 more in the full report
9 fixed9 passed either way4 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+34%
Agent turns
0%
Response time
-23%
Model gemini-3.6-flashMeasured 8/19/2026v318 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Assuming our accepted plan for splitting a monolithic repo into microservices requires durable progress tracking across multiple developer sessions, what path should be recommended post-acceptance?
What was checked, without and with the skill
Checked
Without skill
With skill
The response recommends ultrawork durable checkpoints for progress that must survive sessions.
Missed
Passed
The response includes a one-line rationale explaining why the recommended post-acceptance path fits the work shape.
Missed
Passed
case-06 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md107 linessingle file
Plan
This is a Hermes-native plan workflow skill.
Why This Exists
plan exists to keep planning work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
Do Not Use When
The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.
Examples
Good example:
Prompt: plan: handle a planning request that needs explicit evidence boundaries and a clear stop condition.
Expected behavior: Run plan only after naming the target, evidence boundary, and stop condition.
Why: The request matches the catalog use case and keeps observed evidence separate from prepared guidance.
Bad example:
Prompt: plan: treat casual chat or unaccepted work as if this workflow already produced verified results.
Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing plan.
Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
Completion Checklist
The plan names goals, non-goals, assumptions, acceptance criteria, and verification shape.
Draft recommendations, accepted decisions, and executor handoffs are separate states.
Rejected options or unresolved tradeoffs are recorded before handoff.
Recovery Notes
If acceptance criteria or verification are missing, route back to clarification before handoff.
If assumptions materially affect the plan, keep them visible and avoid treating the plan as accepted.