plan

To generate a Markdown project plan without executing code, provide a goal and constraints to a planning tool that outputs timestamped Markdown files. This process creates auditable documents with task sequencing and success criteria while enforcing strictly read-only behavior.

Plan mode for software development workflows is a planning-only process that converts user goals into concrete, auditable Markdown plans. It enables goal refinement, task sequencing, and risk notes while intentionally avoiding code changes, executions, or external actions.

Yes, you can use planning tools for research tasks and operational workflows. The planning process applies to software development, project planning, and research, generating structured step-by-step planning documents saved as timestamped Markdown files.

You save auditable project plans with timestamps by using a planning tool that automatically writes generated Markdown files to a designated directory like .hermes/plans/. This ensures easy versioning and auditability for your project workflows.

Yes, planning mode restricts code changes and external actions. It enforces planning-only behavior by preventing code modifications, executions, or external actions while still allowing read-only context inspection to inform the plan.

The best way to structure task sequencing and success criteria is to use a planning tool that converts goals into concrete Markdown plans. This approach refines goals, outlines tasks, adds risk notes, and defines success metrics without executing code.