plan

Create markdown implementation plans saved under .hermes/plans/ without modifying files.

Updated May 24, 2026

Search Tags:#workflow #planning #software engineering #markdown #implementation plan

Ready to run

npx skills add https://github.com/anxiety135790/hermes-skills --skill plan-anxiety135790

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/anxiety135790/hermes-skills/tree/main/software-development/plan
Command: npx skills add https://github.com/anxiety135790/hermes-skills --skill plan-anxiety135790

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps when you want planning instead of execution, so the AI produces a concrete markdown plan without modifying project files or running changes.

Core Features & Use Cases

Plan-only workflow: Focuses strictly on analysis and planning rather than implementation.
Workspace-safe output: Saves the plan as a markdown file under .hermes/plans/ for later review and execution.
Useful for scoped tasks: Ideal for software changes, refactors, investigations, or any request where you first want a step-by-step approach before code work begins.

Quick Start

Ask the assistant to create a plan for your current task and save it under .hermes/plans/ in the workspace.

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 project files?▼

To generate an implementation plan without modifying project files, you request a plan-only workflow that outputs a concrete markdown file to .hermes/plans/ containing steps, file impact assessments, and validation strategies while strictly avoiding code execution.

What is a markdown implementation plan for software engineering?▼

A markdown implementation plan is a structured document outlining scoped task analysis, step-by-step execution strategies, affected file paths, test plans, risks, and open questions for software engineering tasks prior to coding.

How do I plan a software refactor before writing any code?▼

You plan a software refactor by using a plan-only workflow to produce a markdown document featuring scoped analysis, step-by-step execution strategy, file impact assessment, and validation planning saved under .hermes/plans/.

Does the plan workflow assess file impact and risks for scoped tasks?▼

Yes, the planning workflow explicitly assesses file impact by listing affected paths and includes validation planning, risks, and open questions for scoped software tasks directly within the generated markdown document.

Can I use this planning approach for software investigations without executing changes?▼

Yes, this approach applies to software investigations, refactors, or any task needing a step-by-step approach, strictly focusing on analysis and planning without executing changes or mutating project files.