plan

Create timestamped Markdown planning documents under .hermes/plans/.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It replaces ad hoc execution with a disciplined planning workflow, generating a markdown plan that defines goals, steps, and validations before any work begins.

Core Features & Use Cases

  • Plan creation and saving: Generates a timestamped plan file in the active workspace under .hermes/plans/.
  • Context inspection without mutation: Reads the current context to inform the plan without changing files.
  • Validation-ready output: Produces a structured plan including goals, steps, risks, and acceptance criteria.

Quick Start

Generate a markdown plan for the current task and save it 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 markdown planning document for software development tasks?

To generate a markdown planning document, the Skill inspects the current workspace context and creates a structured file with goals, steps, risks, and acceptance criteria under .hermes/plans/ with a timestamped filename.

What is plan mode and how does it enforce task planning before execution?

Plan mode enforces task planning by replacing immediate execution with a disciplined workflow that reads context without mutating files, producing validation-ready plans before any software development work begins.

Can I inspect my workspace context without modifying existing project files?

Yes, you can inspect workspace context without modifications because the planning workflow explicitly reads current context to inform the plan while prohibiting any file mutations or external actions.

How do I create a project milestone plan that includes risks and acceptance criteria?

You create a project milestone plan by triggering the workflow, which outputs a validation-ready markdown file documenting your goals, steps, risks, and acceptance criteria for your software development milestones.

Does the generated plan file get saved automatically in the workspace?

Yes, the generated plan file is automatically saved as a markdown document directly in the active workspace under the .hermes/plans/ directory using a timestamped filename.

What is the best way to document software development workflows without triggering code changes?

The best way to document workflows without code changes is using a dedicated planning mode that captures context inspection and task steps into a markdown file, explicitly prohibiting external mutations.