plan

Create a markdown implementation plan with steps, file targets, and risk notes.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/JKhyro/HERMES-AGENT --skill plan-jkhyro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/JKhyro/HERMES-AGENT/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/JKhyro/HERMES-AGENT --skill plan-jkhyro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when you need to think through a task before acting, producing a concrete plan instead of making changes immediately.

Core Features & Use Cases

  • Planning only: Reviews the current context and translates the request into an actionable implementation plan.
  • Workspace-safe output: Saves the plan as a markdown file in the active workspace's .hermes/plans directory.
  • Useful for coding work: Ideal for feature requests, refactors, debugging plans, migration steps, and multi-step automation tasks.

Quick Start

Ask the agent to create a plan for your task and save it in the active 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 create an implementation plan for a coding task without modifying files?

To create an implementation plan without modifying files, the Skill inspects repository context in read-only mode and saves actionable steps to a markdown file in the workspace's .hermes/plans directory.

What is workflow scoping for a repository analysis task?

Workflow scoping for a repository analysis task involves reviewing the current workspace context to translate a feature request or refactor into concrete steps, file targets, and validation notes before execution begins.

Can I generate a markdown plan for debugging and migration steps in my workspace?

Yes, you can generate a markdown plan for debugging and migration steps. The Skill translates these requests into timestamped markdown files containing targeted file paths, validation criteria, and risk notes.

Does the planning process support risk notes and validation criteria?

The planning process supports risk notes and validation criteria by design. Each generated markdown file embeds concrete implementation steps alongside anticipated validation requirements and potential risk factors.

What is the best way to scope a multi-step automation task before writing code?

The best way to scope a multi-step automation task is using a planning-only approach. It analyzes repository context and outputs a structured markdown document with concrete steps and file targets, skipping implementation entirely.

Are there limitations to planning-only turns for repository refactoring?

The main limitation of planning-only turns is that no implementation work is executed. The Skill strictly generates a markdown plan with file targets and risk notes, requiring separate execution afterward.