plan

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

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill plan-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill plan-kaminocorp

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 plan-only mode: the agent inspects context with read-only commands, writes a structured markdown plan, and performs no edits, commits, or mutating actions. ## Core Features & Use Cases - Plan-only enforcement: Prohibits code edits, mutating terminal commands, commits, pushes, and external actions during the planning turn. - Structured plan output: Produces a markdown plan covering goal, context, approach, step-by-step tasks, files likely to change, tests, risks, and open questions. - Workspace-aware saving: Stores plans under .hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md, working across local, docker, ssh, modal, and daytona backends. - Use Case: Before refactoring an authentication module, invoke plan mode to get a saved markdown document listing exact file paths, test targets, and verification steps for team review. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan to the workspace 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 an implementation plan without changing code?▼

Invoke plan mode with your task description. The agent inspects the repository using read-only commands only, then writes a markdown plan with steps, affected files, and tests into the workspace .hermes/plans directory.

Where are plan files saved in the workspace?▼

Plans are saved under .hermes/plans/ with a timestamped filename in the format YYYY-MM-DD_HHMMSS-<slug>.md. The path is relative to the active workspace, so it works across local, docker, ssh, modal, and daytona backends.

What should a good implementation plan include?▼

A concrete plan includes the goal, current context and assumptions, proposed approach, step-by-step tasks, files likely to change, tests and validation steps, plus risks, tradeoffs, and open questions. Code-related plans should list exact file paths and test targets.

Can the agent run commands while in plan mode?▼

Only read-only inspection commands are allowed. Plan mode explicitly prohibits editing project files, running mutating terminal commands, committing, pushing, or performing any external actions.

What happens if the planning request is unclear?▼

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