plan

To generate a Markdown project plan without executing changes, use a planning-only workflow that writes goals, steps, and validation criteria to a document. This ensures your task breakdown remains as actionable documentation without triggering runtime actions or file mutations.

A planning-only workflow for feature scoping produces a concrete Markdown plan describing project goals and steps while strictly enforcing non-execution. It separates the planning phase from implementation, ensuring no code edits or runtime actions occur until the plan is reviewed.

To save a feature kickoff plan to your workspace, the workflow generates a Markdown document and stores it under the .hermes/plans/ directory. The plan is automatically saved with a timestamped filename for easy tracking and retrieval.

Yes, the planning workflow strictly enforces non-execution by preventing any code edits, file mutations, or runtime actions. This guarantees that your project kickoff or task breakdown remains entirely as documentation within the generated Markdown plan.

Yes, you can use this Markdown plan generation for task breakdown in a software engineering workspace. It is specifically designed for feature scoping and project kickoffs, applying a planning mode that outputs structured documentation safely to your active workspace.

The main limitation of this planning-only workflow is that it cannot execute code edits, file mutations, or runtime actions. It is strictly designed to generate and save Markdown plans to .hermes/plans/, meaning you must use separate tools for actual implementation.