plan

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

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/xu1713/openhorse --skill plan-xu1713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/xu1713/openhorse/tree/main/openhorse/openhorse/skills/software-development/plan
Command: npx skills add https://github.com/xu1713/openhorse --skill plan-xu1713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you need a concrete implementation roadmap before touching any code, this Skill enforces a plan-only mode: it inspects the repository read-only and produces a structured markdown plan instead of making changes. ## Core Features & Use Cases - Plan-Only Enforcement: Prevents code edits, mutating commands, commits, and external actions during the planning turn. - Structured Plan Output: Generates plans covering goal, context, approach, step-by-step tasks, files to change, tests, and risks. - Workspace-Aware Saving: Stores 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 document listing exact file paths, test targets, and verification steps for later execution. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan under .hermes/plans/ without modifying any code.

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 and describe the task; the agent inspects the repository with read-only commands and 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 tasks, 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 workspace, 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 only permits read-only inspection commands and writing the plan markdown file itself. It explicitly blocks code edits, mutating terminal commands, commits, pushes, and 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.