skills.rest
nelohenriq
nelohenriqCOMMUNITY
Explore all skills by this author →
GitHub

plan

Inspect repository context and save a structured markdown plan to .hermes/plans/.

1|Updated Mar 22, 2026
Search Tags:#workflow#planning#markdown#workspace#plan-mode#task-planning
One-click install
npx skills add https://github.com/nelohenriq/hermes-agent-plus --skill plan-nelohenriq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/nelohenriq/hermes-agent-plus/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/nelohenriq/hermes-agent-plus --skill plan-nelohenriq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a dedicated planning phase for Hermes users, enabling inspection of the current context and the active workspace to produce a structured, markdown plan instead of executing work.

Core Features & Use Cases

  • Inspect the repository context and workspace constraints to inform planning.
  • Generate a concrete, markdown plan and save it under the active workspace's .hermes/plans/ directory.
  • Output a clear plan structure including goals, approach, step-by-step plan, files likely to change, tests, risks, and open questions.
  • Use Case: A developer requests a plan to implement a feature without performing any code changes or environment side effects.

Quick Start

Invoke plan mode to generate a concrete markdown plan and save it under .hermes/plans/ in the active workspace.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a markdown task plan without executing code changes in my workspace?▼

To create a markdown task plan without executing code changes, invoke plan mode to inspect your repository context and constraints, generating a structured plan saved under .hermes/plans/.

What should a feature planning document include for software development?▼

A feature planning document should include a goal, approach, step-by-step plan, files likely to change, tests, risks, and open questions to thoroughly outline the implementation strategy.

Can I generate a step-by-step implementation plan by inspecting my repository state?▼

Yes, you can generate a step-by-step implementation plan by inspecting your repository state. The planning context evaluates current constraints to produce a structured markdown plan.

Does plan mode save generated plans to a specific workspace directory?▼

Yes, plan mode saves generated plans to a specific workspace directory. The concrete, actionable markdown plan is automatically saved under the active workspace's .hermes/plans/ folder.

What is the best way to outline risks and open questions before starting development?▼

The best way to outline risks and open questions before starting development is to use a dedicated planning phase that inspects workspace constraints and outputs a structured markdown plan.

When should I use a dedicated planning phase instead of directly executing work?▼

You should use a dedicated planning phase instead of directly executing work when you need to inspect the repository context and evaluate constraints to produce a structured plan without environment side effects.

Related Skills

Explore More Software Engineering Skills→
LibPDF-jsLibPDF-js
1.8k

create-plan

Generate Markdown plan files with frontmatter metadata under .agents/plans/.

Official
Intermediate
HughYauHughYau
2.4k

writing-plans

Generates step-by-step implementation plans for multi-step software development tasks.

Community
Intermediate
davpatel605-beepdavpatel605-beep

code-wiki

Generate structured wiki documentation and Mermaid architecture diagrams from source code.

Community
Advanced
vvieira010-pixelvvieira010-pixel

udl-lesson-auditor

Audit lesson plans for accessibility barriers using Universal Design for Learning principles.

Community
Intermediate