plan

To generate a markdown plan without modifying the repository, this Skill inspects context in read-only mode and outputs a standalone, timestamped markdown file to the .hermes/plans directory. It enforces a non-destructive, non-action policy during the planning phase.

The best way to formalize workflow planning before execution is generating a concrete, deterministic markdown plan. This approach outlines required steps and constraints upfront, reducing risk by ensuring teams agree on the task plan before any code changes occur.

Yes, this planning tool supports documentation projects as well as software development. It applies to planning-only scenarios across both domains, generating structured markdown plans for any task requiring deterministic steps before actual execution begins.

Yes, you can use this for task management to inspect repository context and constraints. It analyzes the active workspace read-only to inform the step-by-step plan, ensuring the generated markdown accurately reflects your project's current state and limitations.

To save generated task plans, the Skill automatically writes the output markdown file to the active workspace's .hermes/plans directory. The resulting file uses a standalone markdown format with a timestamped name for easy tracking and historical reference.