Help us improve
Share bugs, ideas, or general feedback.
From dev-workflow-skills
Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes/plans/` directory, and do not execute the work.
npx claudepluginhub rnben/hermes-skills --plugin dev-workflow-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/dev-workflow-skills:planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the user wants a plan instead of execution.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Creates and presents web-based slidedecks using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use for technical presentations, conference talks, code walkthroughs, or teaching materials.
Share bugs, ideas, or general feedback.
Use this skill when the user wants a plan instead of execution.
For this turn, you are planning only.
.hermes/plans/.Write a markdown plan that is concrete and actionable.
Include, when relevant:
If the task is code-related, include exact file paths, likely test targets, and verification steps.
Save the plan with write_file under:
.hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.mdTreat 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/.
/plan, infer the task from the current conversation context.