plan

Generate a structured markdown plan with goals, steps, and validation criteria.

Updated May 21, 2026
One-click install
npx skills add https://github.com/samlaggz/hermes-agent-sam --skill plan-samlaggz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/samlaggz/hermes-agent-sam/tree/main/backup/skills/software-development/plan
Command: npx skills add https://github.com/samlaggz/hermes-agent-sam --skill plan-samlaggz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan mode prevents ad hoc execution by producing a clear, markdown-based plan that outlines goals, assumptions, approach, steps, and validation without performing any changes.

Core Features & Use Cases

  • Plan generation: Produce a concrete markdown plan to document goals, tasks, and validation criteria.
  • Audit-ready output: Includes goals, assumptions, step-by-step tasks, success criteria, and risks.
  • Non-execution by design: All planning output is written to the workspace without mutating files or running commands.

Quick Start

Save a concrete markdown plan to .hermes/plans/ for the current task.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a software development plan without executing code changes?

Generate a structured markdown plan without executing actions by outlining goals, assumptions, approach, and validation steps. The output is written to the workspace without mutating files or running commands.

What is plan-first mode for software development planning?

Plan-first mode prevents ad hoc execution by producing a clear, markdown-based plan that outlines goals, assumptions, approach, steps, and validation without performing any changes to the repository.

Can I create a markdown plan for feature proposals that includes risks and validation criteria?

Yes, you can create an audit-ready markdown plan that documents goals, assumptions, step-by-step tasks, success criteria, and risks for feature proposals and repository changes.

Does this planning tool save plans automatically with timestamps?

Yes, the planning tool saves plans automatically to the .hermes/plans/ directory using a timestamped filename, ensuring each plan is tracked and auditable.

What's the best way to document sprint planning steps without modifying files?

Use a non-execution planning approach to document sprint planning steps. The generated plan includes frontmatter-driven metadata and validation criteria, writing output to the workspace without mutating files.

When should I not use a non-mutating markdown plan for repository changes?

Avoid using a non-mutating markdown plan when immediate code execution or file modifications are required, as this approach is designed solely for planning and documentation without applying changes.