plan

Inspect context and write a timestamped markdown plan to .hermes/plans/.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables Hermes to generate a concrete plan without executing work, keeping decisions in a planned, auditable format.

Core Features & Use Cases

  • Plan-only generation: Inspects context and outputs a markdown plan without performing any mutations or external actions.
  • Plan persistence: Saves the plan to the active workspace under .hermes/plans/ with a timestamped filename for traceability.
  • Non-execution by default: Ensures no code changes, commits, or runs outside of plan creation.

Quick Start

Provide a concrete plan and save it to the active workspace 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 an actionable markdown plan in my workspace without executing code?

To generate an actionable markdown plan without executing code, this skill inspects your context and outputs a timestamped markdown file. It defers execution entirely, ensuring no files are mutated or commands run outside of plan creation.

What is the best way to outline task dependencies and validation criteria before committing changes?

The best way to outline task dependencies and validation criteria before committing changes is to compute a concrete plan. This process produces a markdown document detailing the steps while strictly avoiding any actual workspace mutations or external actions.

How does task-planning mode keep decisions in an auditable format?

Task-planning mode keeps decisions auditable by saving the generated plan to the active workspace under .hermes/plans/ with a timestamped filename. This ensures every planning decision is traceable without executing the actual work.

Can I use this planning approach to prevent automated agents from running commands and mutating files?

Yes, you can use this planning approach to prevent automated agents from running commands and mutating files. It enforces non-execution by default, guaranteeing no code changes, commits, or external runs occur during the plan generation phase.

Does plan generation require any external dependencies or specific workspace components?

Plan generation requires no external dependencies or specific components, operating solely within the active workspace. It simply requires a context to inspect, producing a markdown plan file saved locally without needing additional environment setups.