plan

Generate timestamped Markdown plans for Hermes workflows without executing them.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/quiznat/Hermes_Sapho --skill plan-quiznat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/quiznat/Hermes_Sapho/tree/main/.hermes/skills/software-development/plan
Command: npx skills add https://github.com/quiznat/Hermes_Sapho --skill plan-quiznat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When users need a clear, executable-free blueprint for Hermes workflows, this skill generates a concise, actionable plan instead of performing any changes.

Core Features & Use Cases

  • Plan-only mode: generates a detailed, ready-to-save plan that can be reviewed before any action.
  • Non-destructive: does not modify files or run commands; focus is on documentation and strategy.
  • Save-ready output: writes a timestamped Markdown plan to the active workspace at .hermes/plans/.

Quick Start

Ask me to plan and I will generate a concrete markdown plan saved under .hermes/plans/ with a timestamped filename.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate a non-destructive workflow plan before implementing changes?

A workflow plan in plan mode outlines steps, dependencies, risks, and validation without modifying files or running commands. It provides a non-destructive strategy document saved as Markdown for review before implementation.

How do I create a timestamped markdown plan for Hermes actions?

To create a timestamped markdown plan, ask the skill to plan Hermes actions. It generates a ready-to-save markdown file with a timestamped filename stored directly in the .hermes/plans/ directory of your active workspace.

Can I outline workflow steps and risks without executing commands in my workspace?

Yes, you can outline workflow steps and risks without execution. The plan mode operates non-destructively, meaning it does not modify files or run commands, focusing entirely on generating strategy and documentation.

What is the best way to document task dependencies and validation before modifying a project?

The best way to document task dependencies and validation is using a plan-only mode that generates an executable-free blueprint. This approach saves a concise, actionable markdown plan for review before any workspace changes occur.

Does generating a plan for Hermes workflows require write access to the project files?

Generating a plan for Hermes workflows does not require write access to project files. The skill requires only read-only access to project context to safely outline steps while maintaining a non-destructive workflow.

When should I not use an automated plan generation approach for my tasks?

You should not use automated plan generation when you need immediate code execution or file modifications. This approach is strictly non-destructive, focusing solely on generating strategy and documentation rather than implementing changes.