What problem does it solve? It prevents premature implementation by enforcing a structured planning phase between brainstorming and execution, producing a concrete, reviewable markdown plan before any code changes happen. ## Core Features & Use Cases - Planning-only mode: Inspects the repository with read-only commands and writes a plan without editing project files, running mutating commands, or committing changes. - Mandatory three-phase gate: Enforces Brainstorm → Plan → Execute, blocking planning if brainstorming never happened and blocking execution until the user approves the plan. - Timestamped plan output: Saves plans as .hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md relative to the active workspace, working across local, docker, ssh, modal, and daytona backends. - Use Case: Before adding user authentication, invoke /plan add user authentication to get a saved plan covering the goal, approach, files to change (e.g., src/auth.py, tests/test_auth.py), risks, and verification steps, then approve it before any code is written. ## Quick Start Ask the agent to plan a task with a command like "/plan add user authentication" and it will inspect the repo read-only, save a detailed markdown plan under .hermes/plans/, and wait for your approval before executing.