plan

Write a planning-only markdown plan and save it to .hermes/plans/.

3|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill plan-twjarviszyra-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/twjarviszyra-web/hermes-unbound/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill plan-twjarviszyra-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when you need a concrete implementation plan instead of immediate execution, so the assistant can organize the work before making any changes.

Core Features & Use Cases

  • Planning-only workflow: Reviews the request and current context, then produces a practical markdown plan.
  • Workspace-safe output: Saves the plan in the active workspace under the .hermes/plans/ directory.
  • Use case: Use it when you want a teammate-style action plan for a feature, bug fix, refactor, or investigation without touching project files.

Quick Start

Use the plan skill to write a markdown implementation plan for the current task and save it in the workspace’s .hermes/plans/ directory.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an implementation plan without modifying my workspace code?

To generate an implementation plan without modifying code, you can use a planning-only markdown workflow that performs read-only analysis of your context and saves the output to a directory like .hermes/plans/.

When do I need a markdown planning file before starting a software feature?

You need a markdown planning file when you want to organize next steps and inspect context for a feature, bug fix, or refactor before execution, ensuring the assistant avoids making direct code edits.

What is the best way to structure a workflow plan for a complex refactor?

The best way to structure a workflow plan for a complex refactor is to generate a timestamped markdown document that outlines the practical steps and context review, saved directly in your active workspace.

Can I create a read-only action plan for a bug investigation without touching project files?

Yes, you can create a read-only action plan for a bug investigation that restricts the assistant to analysis only, preventing any mutating terminal actions or file edits during the planning phase.

Does the planning workflow support saving output to a specific directory structure?

Yes, the planning workflow supports saving output to a specific directory structure, automatically writing the generated markdown plan into the .hermes/plans/ folder within your active workspace.

What are the limitations of a read-only planning mode for software development?

The limitation of read-only planning mode is that it strictly prohibits code edits and mutating terminal actions, meaning you must switch to an execution mode to actually implement the saved markdown plan.