skills.rest
superfhp
superfhpCOMMUNITY
Explore all skills by this author →
GitHub

plan

Writes actionable markdown implementation plans to .hermes/plans/ without executing code.

Updated May 13, 2026
Search Tags:#workflow#planning#markdown#software development#implementation plan#plan mode
One-click install
npx skills add https://github.com/superfhp/lumi-agent-body --skill plan-superfhp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/superfhp/lumi-agent-body/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/superfhp/lumi-agent-body --skill plan-superfhp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you need a concrete implementation strategy before touching any code, this Skill enforces a planning-only mode that produces a structured markdown plan instead of making premature changes to your project. ## Core Features & Use Cases - Plan-Only Mode: Prevents code edits, mutating commands, commits, and external actions while allowing read-only repository inspection. - Structured Plan Output: Generates plans covering goals, assumptions, step-by-step approach, files to change, tests, risks, and open questions. - Workspace-Aware Saving: Stores plans as timestamped markdown files under .hermes/plans/ relative to the active workspace, working across local, docker, ssh, modal, and daytona backends. - Use Case: Before refactoring a large module, invoke plan mode to get a written plan with exact file paths, test targets, and verification steps saved to your workspace for later execution. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan to .hermes/plans/ without modifying any code.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create an implementation plan without changing code?▼

Invoke plan mode with your task description, and the agent inspects the repository with read-only commands, then writes a markdown plan to .hermes/plans/. No project files are edited and no mutating commands are run.

What should a good software implementation plan include?▼

A good plan includes the goal, current context and assumptions, proposed approach, step-by-step actions, files likely to change, tests and validation steps, plus risks and open questions. Code-related plans should list exact file paths and test targets.

Where are plan files saved in the workspace?▼

Plans are saved as timestamped markdown files under .hermes/plans/ relative to the active working directory. This path works consistently across local, docker, ssh, modal, and daytona backends.

Can plan mode run terminal commands or edit files?▼

Plan mode only permits read-only inspection commands and writing the plan markdown file itself. It cannot edit project files, run mutating commands, commit, push, or perform external actions.

When should I use plan mode instead of direct implementation?▼

Use plan mode when a task is complex, touches many files, or carries risk, so you can review the approach first. Skip it for trivial changes where a written plan adds no value.

Related Skills

Explore More Software Engineering Skills→
thesyntaxninjathesyntaxninja
2

writing-plans

Generate structured multi-step plans with goals, context, and acceptance criteria.

Community
Intermediate
alphabeenalphabeen
3

agentic-review-work

Audit a codebase against a plan document and produce a PASS/FAIL review.

Community
Advanced
ClyptAIClyptAI

requesting-code-review

Automate peer-review workflows for code changes using a specialized subagent.

Official
Advanced
statsclawstatsclaw
89

simplified-workflow

Run a 4-step pipeline for small routine code changes.

Official
Intermediate