plan

To generate a structured plan, this tool converts your task intent into a markdown outline covering goals, steps, dependencies, and risks. The resulting plan is saved as a timestamped file under the .hermes/plans/ directory for later reference.

Outlining architectural risks and assumptions is handled by generating a markdown-based plan. It structures your intent into sections for assumptions, approach, risks, and open questions, saving the document directly to your workspace's .hermes/plans/ folder.

No, this planning mode explicitly limits scope to planning only and does not execute any actions. It strictly generates an actionable plan outline and saves it as a markdown file, preventing scope creep and miscommunication before execution begins.

Yes, the generated plan includes specific sections for tests and open questions. It transforms your target task intent into a comprehensive markdown outline that documents dependencies, risks, approach, and testing requirements.

Saving a strategy plan to the workspace happens automatically when the tool generates your markdown outline. It writes the resulting plan to the .hermes/plans/ directory using a timestamped filename for easy tracking and retrieval.

You need a markdown plan file when preparing for a software feature, architectural review, or migration task. It provides a structured outline of goals and steps, ensuring alignment and reducing scope creep before any code runs.