plan

You can generate an actionable Markdown plan using a planning-only mode that prevents code edits or mutating actions. This ensures you produce structured, timestamped plans saved under .hermes/plans/ without altering your codebase.

The best way to structure sprint planning is to generate a concrete Markdown plan that decomposes tasks and scopes features. This produces a timestamped file in .hermes/plans/ and outputs a concise summary for team reference.

To save and reference project management plans later, generate a structured Markdown file with a timestamped filename. This deterministic approach eliminates ad-hoc notes and stores plans directly in .hermes/plans/ for future access.

Yes, plan mode enforces planning-only behavior that prevents accidental code edits or mutations. It operates exclusively to generate actionable Markdown plans, making it safe for feature scoping without modifying existing project files.

A dedicated planning-only mode eliminates unstructured, ad-hoc decision notes by producing deterministic, actionable Markdown plans. It automatically saves timestamped files and outputs a concise summary, ensuring plans are consistently formatted and referenceable.