plan

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you need a concrete, actionable implementation plan before touching any code, this Skill enforces a strict planning-only mode: it inspects the repository with read-only operations and produces a structured markdown plan saved to your workspace, preventing premature or accidental code changes. ## Core Features & Use Cases - Plan-Only Enforcement: Explicitly blocks code edits, mutating terminal commands, commits, pushes, and external actions during the planning turn. - Structured Plan Output: Generates plans covering goal, context, approach, step-by-step actions, files likely to change, tests, risks, and open questions. - Workspace-Aware Saving: Stores plans as timestamped markdown files under .hermes/plans/, compatible with local, docker, ssh, modal, and daytona backends. - Use Case: Before refactoring a payment module, invoke plan mode to get a written plan listing exact file paths, test targets, and verification steps, then review it with your team before any implementation begins. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan to .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 before writing code?▼

Invoke plan mode with your task description, and the agent inspects the repository read-only, then writes a markdown plan with goals, steps, affected files, and tests to .hermes/plans/. No code is modified during this 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, exact file paths likely to change, test targets, verification steps, and risks or open questions. This Skill structures output around exactly those sections.

Where are the generated plan files saved?▼

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 works across local, docker, ssh, modal, and daytona backends.

Can plan mode accidentally modify my repository?▼

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

When should I use plan mode instead of direct implementation?▼

Use plan mode for complex or risky changes where you want to review the approach first, coordinate with teammates, or document decisions. Skip it for trivial, well-understood edits where planning overhead adds no value.