plan

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

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill plan-vivekgoquest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/vivekgoquest/hermes-agent-stable/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/vivekgoquest/hermes-agent-stable --skill plan-vivekgoquest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you want a concrete, actionable implementation plan before any code is written, this Skill enforces a planning-only mode: it inspects the repository read-only and produces a detailed markdown plan saved to your workspace, preventing premature or accidental changes. ## Core Features & Use Cases - Planning-Only Guardrails: Prohibits code edits, mutating commands, commits, and external actions during the planning turn. - Structured Plan Authoring: Generates plans with goal, context, step-by-step bite-sized tasks (2-5 minutes each), exact file paths, complete code examples, test commands, and risks. - TDD and Handoff Ready: Embeds test-driven development cycles and frequent commits per task, then hands off to subagent-driven-development for execution. - Use Case: Ask for a plan to add user authentication, and receive a saved markdown file with exact files to create, failing tests to write first, verification commands, and commit steps. ## 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 create an implementation plan before writing code?▼

Invoke plan mode with your feature request, and the agent inspects the repository read-only, then writes a markdown plan to .hermes/plans/ with goal, step-by-step tasks, exact file paths, code examples, and verification commands. No project files are modified.

What should a good software implementation plan include?▼

A good plan includes the goal, current context and assumptions, proposed approach, bite-sized tasks of 2-5 minutes each, exact file paths, complete copy-pasteable code, exact test commands with expected output, and risks or open questions.

Where are plan files saved in the workspace?▼

Plans are saved under .hermes/plans/ relative to the active working directory, using timestamped filenames like YYYY-MM-DD_HHMMSS-slug.md. If the runtime provides a specific target path, that exact path is used instead.

Can plan mode accidentally modify my code or run commands?▼

No. Plan mode explicitly prohibits editing project files other than the plan markdown, running mutating terminal commands, committing, pushing, or performing external actions. Only read-only inspection of the repository is allowed.

When should I not use a full implementation plan?▼

The skill recommends always planning before multi-step features, complex requirements, or subagent delegation. It argues against skipping even for simple features, since unstated assumptions are a common source of bugs.