plan

Generate a structured markdown execution plan in the .hermes/plans/ directory.

641|104|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/eastreams/loong --skill plan-eastreams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/eastreams/loong/tree/main/skills/plan
Command: npx skills add https://github.com/eastreams/loong --skill plan-eastreams

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the need to manually draft execution plans by automatically generating structured markdown plans without modifying any repository files or running code.

Core Features & Use Cases

  • Read‑only analysis: Inspects the repository and conversation context safely.
  • Markdown plan generation: Creates a detailed plan saved in the .hermes/plans/ directory.
  • Safety guarantees: Never mutates files, runs commands, or performs external actions. Ideal for developers and teams needing clear project roadmaps before implementation.

Quick Start

Invoke the plan skill with /plan followed by your task description to generate a markdown plan saved in .hermes/plans/.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate a markdown plan for software development without modifying repository files?

To generate a markdown plan without modifying repository files, use a read-only planning skill that inspects your codebase and saves a structured markdown file into the .hermes/plans/ directory. It never mutates files or executes terminal commands.

Can I create a project roadmap without running any code or terminal commands?

Yes, you can create a project roadmap without running any code by using a read-only analysis tool that generates a detailed markdown plan. It safely inspects the repository context and avoids executing terminal commands or performing external actions.

What is the best way to design a workflow using markdown plans?

The best way to design a workflow using markdown plans is to invoke a read-only planning skill with your task description. It analyzes the repository context and automatically generates a structured markdown document saved in the .hermes/plans/ directory.

Does the plan skill work with read-only repository constraints?

Yes, the plan skill works with read-only repository constraints by design. It strictly inspects the repository and conversation context while guaranteeing it never mutates files, runs commands, or performs external actions.

Where are the generated markdown plans stored?

Generated markdown plans are stored in the .hermes/plans/ directory within your repository. The tool creates a detailed markdown file there during the planning process while keeping the rest of your repository unchanged.

Why should I use a read-only planning tool instead of manually drafting execution plans?

You should use a read-only planning tool instead of manually drafting execution plans to eliminate manual effort and ensure safety. It automatically generates structured markdown plans from your conversation context while guaranteeing no repository files are mutated.