plan

To generate a Markdown plan without code execution, use a planning mode that outputs concrete, step-by-step written plans. It saves the ready-to-use Markdown file to your workspace, ensuring a clear workflow design before implementation begins.

The best way to create feature roadmaps is using a dedicated Markdown planning mode. It generates a thorough, actionable document for your software project and saves it with a timestamped filename, preventing premature code execution.

No, plan mode does not modify repository files or run terminal commands. It operates in a read-only context to observe constraints, ensuring your codebase remains untouched while it generates and saves the Markdown plan.

Yes, you can use Markdown planning for team workflows and research tasks. It generates concrete, actionable plans applicable to various contexts, writing a thorough document to help teams align before any actual implementation starts.

Generated Markdown plans are saved directly to the workspace under the .hermes/plans/ directory. Each plan is stored with a timestamped filename, ensuring organized tracking and easy retrieval for future reference.

You need a written plan instead of direct code execution when a task requires thorough, step-by-step preparation before implementation. This approach applies to software projects, research, and team workflows where a read-only Markdown plan is essential.