plan

Generate a project plan by reading the current workspace context and writing a structured Markdown document with goals, steps, and validation points to the .hermes/plans/ directory using a timestamped filename, ensuring no execution actions are performed.

Creating structured Markdown plans involves capturing project goals, approach, tasks, and validation criteria into a single document, which is then saved with a timestamped filename in the .hermes/plans/ workspace folder for full traceability.

This planning approach works for both small features and large project workflows across teams by generating formal Markdown documents that establish clear delivery expectations and validation points before any implementation begins.

You can automate workflow planning without modifying your codebase because the process requires read-only access to context and solely writes a new Markdown plan file to the .hermes/plans/ directory, leaving existing files untouched.

Generate a formal plan document before starting software development work to reduce misalignment and wasted effort by establishing concrete goals, actionable steps, and validation criteria in a timestamped Markdown file prior to execution.

Validate project goals and steps before implementation by generating a context-driven Markdown plan that explicitly outlines validation points and delivery expectations, saving it to .hermes/plans/ for team review.