plan

Generate a timestamped markdown plan document under .hermes/plans/.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Harries/hermes-agent --skill plan-harries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Harries/hermes-agent/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/Harries/hermes-agent --skill plan-harries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan mode automates the creation of structured, actionable planning documents from current context, removing manual drafting effort.

Core Features & Use Cases

  • Generate a concise markdown plan from the active task context.
  • Save the plan to the active workspace under .hermes/plans/ with a timestamped filename.
  • Enforce read-only planning behavior that does not mutate or execute code in repositories.

Quick Start

Invoke plan mode to generate a markdown plan from the current task and save it to the workspace under .hermes/plans/.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a markdown plan from current task context?

To generate a markdown plan, invoke plan mode to automatically extract context and create a structured document. The plan is saved to the workspace under .hermes/plans/ with a timestamped filename.

What is the best way to automate planning documents for feature work?

Automating planning documents is done by invoking plan mode, which drafts a concise markdown outline from active context. This removes manual drafting effort and saves the final plan to .hermes/plans/.

Does planning mode execute code or modify files outside the plan path?

Planning mode enforces read-only behavior and does not execute code or modify files outside the plan path. It uses read-only context when necessary and only saves the final markdown plan under .hermes/plans/.

How are markdown plan files named when saved to a Hermes workspace?

Markdown plan files are saved with a deterministic timestamped filename. The format follows .hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md to ensure chronological organization.

Can I use this planning automation for research tasks across any workspace?

Yes, this planning automation applies to Hermes planning tasks across any workspace. It supports outlining steps for both feature work and research, generating structured markdown plans accordingly.

Do I need any dependencies to create deterministic markdown plans?

No dependencies are required to create deterministic markdown plans. The plan mode operates independently using current context to generate and save the final document under .hermes/plans/.