plan

Writes actionable markdown implementation plans to .hermes/plans/ without executing code.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Junkfooooood/hermes-governance --skill plan-junkfooooood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Junkfooooood/hermes-governance/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/Junkfooooood/hermes-governance --skill plan-junkfooooood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you need a concrete implementation strategy before touching code, this Skill enforces a planning-only mode that produces a structured markdown plan instead of making changes, preventing premature or accidental modifications to your project. ## Core Features & Use Cases - Plan-Only Enforcement: Blocks code edits, mutating commands, commits, and external actions while allowing read-only inspection of the repository. - Structured Plan Output: Generates plans covering goals, assumptions, step-by-step approach, files likely to change, tests, risks, and open questions. - Workspace-Aware Saving: Stores plans as timestamped markdown files under .hermes/plans/ relative to the active workspace, working across local, docker, ssh, modal, and daytona backends. - Use Case: Before refactoring a large module, invoke plan mode to get a written plan with exact file paths, test targets, and verification steps saved to your workspace for review and later execution. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan to .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 create an implementation plan without changing code?

Invoke plan mode with your task description, and the agent inspects the repository with read-only commands, then writes a markdown plan to .hermes/plans/. No files are edited and no mutating commands are run during the planning turn.

What should a good software implementation plan include?

A good plan includes 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.

Where are plan files saved in the workspace?

Plans are saved as timestamped markdown files under .hermes/plans/ relative to the active working directory, using the format YYYY-MM-DD_HHMMSS-slug.md. This path works consistently across local, docker, ssh, modal, and daytona backends.

Can plan mode run terminal commands or edit files?

Plan mode permits only read-only inspection commands and writing the plan markdown file itself. It explicitly blocks code edits, mutating terminal commands, commits, pushes, and any external actions.

What happens if the planning request is unclear?

If the task is genuinely underspecified, the agent asks a brief clarifying question instead of guessing. When the request is clear or inferable from conversation context, it writes the plan directly and replies with a summary and saved path.