plan

Generate a timestamped markdown implementation plan under .hermes/plans/.

Updated May 10, 2026
One-click install
npx skills add https://github.com/Mateus2411/Hermes-PersonalBot --skill plan-mateus2411
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Mateus2411/Hermes-PersonalBot/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/Mateus2411/Hermes-PersonalBot --skill plan-mateus2411

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps users turn ambiguous goals into a concrete, step-by-step implementation roadmap without immediately changing code or running risky commands.

Core Features & Use Cases

  • Plan-only workflow: Produces a markdown plan without executing or implementing code.
  • Workspace-safe output: Saves the plan into .hermes/plans/ for traceable execution planning.
  • Actionable structure: Includes goal, assumptions, approach, step-by-step actions, likely file changes, validation steps, and risks.

Quick Start

Ask the AI: “Create a plan to implement the requested feature, and save it under the 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 roadmap for a software development task?

An implementation roadmap is generated by creating a structured markdown plan that outlines the approach, file changes, tests, and risks before taking action. It turns ambiguous goals into a concrete, step-by-step workflow without executing code.

What is the best way to plan code changes without modifying the repository?

The best way to plan code changes without modifying the repository is to generate a plan-only markdown file. This approach strictly prohibits mutating terminal commands and external actions, ensuring the workspace remains completely safe.

Can I save a development workflow plan as a markdown file?

Yes, you can save a development workflow plan as a timestamped markdown file. It is automatically saved under the .hermes/plans/ directory to provide traceable execution planning and keep your workspace organized.

Does the plan generation workflow include actionable verification steps?

Yes, the plan generation workflow includes actionable verification steps. The generated markdown structure encompasses the goal, assumptions, approach, step-by-step actions, likely file changes, validation steps, and potential risks.

When should I not use an automated implementation plan generator?

You should not use an automated implementation plan generator when you need immediate code execution or direct repository modifications. This approach is strictly for planning and does not perform code execution or mutate terminal commands.