plan

Writes a markdown implementation plan into the workspace's .hermes/plans/ directory without executing changes.

14|5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill plan-mlt-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/MLT-OSS/hermes-agent-go/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill plan-mlt-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you want a concrete, reviewable implementation plan before any code is touched, this Skill enforces a planning-only mode: the agent inspects context with read-only operations and produces a structured markdown plan instead of mutating your project. ## Core Features & Use Cases - Plan-only enforcement: No code edits, no mutating terminal commands, no commits or external actions during the turn. - Structured plan output: Generates goal, context, approach, step-by-step plan, files to change, tests, risks, and open questions. - Workspace-aware saving: Saves plans as timestamped markdown files under .hermes/plans/, working across local, Docker, SSH, Modal, and Daytona backends. - Use Case: Before refactoring a module, invoke plan mode to get a saved plan listing exact file paths, test targets, and verification steps that you can review and approve first. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan under .hermes/plans/ without making any code changes.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I get an AI agent to write a plan before coding?

Invoke plan mode with your task description, and the agent will inspect the repository with read-only commands and write a markdown plan covering goal, approach, steps, files to change, and tests. No code is modified during the planning turn.

Where are plan files saved in Hermes?

Plans are saved as timestamped markdown files under .hermes/plans/ relative to the active workspace, using the format YYYY-MM-DD_HHMMSS-slug.md. The path works across local, Docker, SSH, Modal, and Daytona backends.

Can the plan skill modify or run code while planning?

No. Plan mode explicitly forbids editing project files, running mutating terminal commands, committing, pushing, or performing external actions. Only read-only inspection and writing the plan markdown file are allowed.

What should a good implementation plan include?

A plan should include the goal, current context and assumptions, proposed approach, step-by-step actions, files likely to change, tests and validation steps, plus risks and open questions. For code tasks it should list exact file paths and test targets.

What happens if my planning request is underspecified?

If the request is clear, the plan is written directly; if no explicit instruction accompanies the command, the task is inferred from conversation context. If genuinely ambiguous, the agent asks a brief clarifying question instead of guessing.