plan

You can create a development plan without code execution by generating a structured markdown file that outlines steps, file changes, and validation strategies while keeping repository inspection strictly read-only. This prevents unintended modifications during the planning phase.

A software development plan should include project goals, assumptions, the technical approach, detailed steps, expected file changes, testing strategies, and potential risks. Structuring this in markdown ensures the plan is readable and easy to maintain.

You outline file changes and validation strategies by inspecting the repository context in a read-only manner, then documenting the required modifications and test criteria in a comprehensive markdown development plan before any actual implementation begins.

No, this planning workflow does not alter your existing repository files. It performs read-only inspection of the codebase and writes the generated development plan to a separate timestamped markdown file, ensuring your source code remains untouched.

Generated markdown development plans are saved automatically as timestamped files within the .hermes/plans/ directory. This automated saving keeps your project planning history organized and easily accessible for future reference.

The best way to document software project risks and assumptions is by generating a structured markdown plan. This approach systematically records goals, assumptions, and risks alongside implementation steps, reducing manual outlining errors.