plan

To generate an actionable markdown plan without modifying project files, inspect the current context to produce a concrete task breakdown and risk assessment, saving the output to .hermes/plans/ with a timestamped filename. This ensures project files remain unmutated during feature scoping.

Scoping software features and assessing risks requires inspecting the current project context to produce a detailed, shareable markdown plan. This approach prevents unvalidated work by formalizing task breakdowns and execution readiness checks before any code changes occur.

Yes, you can create a project management plan that saves automatically to your active workspace. The plan is generated as a timestamped markdown file under the .hermes/plans/ directory, providing a concrete record for workflow planning without executing work.

Plan-first workflow execution requires no specific dependencies or components. It operates as a standalone community skill that inspects context and outputs markdown files directly into the active workspace, ensuring zero entry barriers for software project planning.

Using a markdown plan generator avoids unvalidated work by forcing a detailed review of task breakdowns and risk assessments before execution. It produces a shareable, timestamped document that teams can validate, preventing unintended project file mutations.

Context inspection for software project planning is limited to generating markdown documents and does not execute work or mutate project files. It focuses strictly on feature scoping and task breakdown, meaning teams must manually implement the saved actionable plan.