plan

Write a markdown project plan without executing code or modifying files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you outline and document a plan without making any code or file changes, perfect for pre-planning phases of a project.

Core Features & Use Cases

  • Markdown Planning: Write and save a markdown plan file directly into the workspace.
  • Non-Execution: The skill only writes the plan; it does not execute any code or modify project files.
  • Use Case: Ideal for project planning, where you want to detail the project approach and steps without jumping into implementation.

Quick Start

Activate the 'plan' skill to create a markdown plan for your project in the '.hermes/plans/' directory.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a project plan in markdown without executing code or modifying files?

To create a markdown project plan without code execution, use a non-executing planning mode that writes and saves your outlined steps directly into the workspace without triggering file modifications.

What is plan mode for project planning and how does it work?

Plan mode for project planning is a pre-implementation phase mechanism that generates a markdown document detailing your project approach, ensuring no code runs and no existing project files are altered.

Can I document project workflows and steps without making changes to the workspace?

Yes, you can document project workflows without making workspace changes by using a non-executing markdown planning approach that saves your outlined steps while strictly preventing file modifications.

What is the best way to outline a project approach before implementation?

The best way to outline a project approach before implementation is generating a markdown plan file that details your workflow steps, allowing you to review the strategy without executing code.

Does this markdown planning method save plans to a specific directory?

Yes, this markdown planning method saves generated project plans directly into a designated '.hermes/plans/' directory within your workspace, keeping your pre-implementation documentation organized.

When should I not use a non-executing markdown plan for project documentation?

You should not use a non-executing markdown plan when your project requires immediate code execution or direct file modifications, as this approach strictly writes documentation without applying changes.