plan

An implementation plan for software development is generated as a concrete markdown file without executing code changes. It provides a staged workflow approach, including likely file changes and validation tests, saving the output to `.hermes/plans/`.

Documenting a workflow plan before modifying software involves generating a timestamped markdown file that captures goals, assumptions, step-by-step actions, and risk tradeoffs. This plan-only approach ensures alignment on scope without risking unintended code changes.

Creating a staged implementation plan that includes tests and file changes is the core function. The generated markdown deliverable explicitly lists likely file modifications, validation tests, open questions, and step-by-step workflow instructions.

The planning workflow saves deliverables directly to the workspace for later reference. Plans are persisted as timestamped markdown files in the `.hermes/plans/` directory, ensuring the implementation guide remains accessible and easy to track.

Using a plan-only approach prevents unintended code changes and avoids running external commands during the scoping phase. It turns a request into a clear, actionable implementation guide with defined tests and file changes before any development begins.

Limitations of generating markdown plans include strict plan-only behavior and read-only inspection. It cannot perform code changes, execute commands, or take external actions, functioning solely to produce a staged implementation guide.