skills.rest
AvaTar-ArTs
AvaTar-ArTsCOMMUNITY
Explore all skills by this author →
GitHub

plan

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

Updated Jul 10, 2026
Search Tags:#workflow#planning#markdown#software development#implementation plan#read-only#plan mode
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill plan-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill plan-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you need a concrete, actionable implementation plan before touching any code, this Skill enforces a strict plan-only mode: it inspects the repository with read-only commands and produces a structured markdown plan saved to your workspace, with zero risk of accidental edits or mutations. ## Core Features & Use Cases - Plan-Only Enforcement: Explicitly blocks code implementation, file edits, mutating terminal commands, commits, and external actions during the planning turn. - Structured Plan Output: Generates plans covering goal, context, approach, step-by-step actions, files likely to change, tests, risks, and open questions. - Workspace-Aware Saving: Writes timestamped plans to .hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md, working across local, docker, ssh, modal, and daytona backends. - Use Case: Before refactoring a module, invoke plan mode to get a written plan listing exact file paths, test targets, and verification steps, then review it before any code changes happen. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan under .hermes/plans/ without making any code changes.

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 and describe the task. The agent inspects the repository with read-only commands only, then writes a markdown plan with steps, affected files, and tests to .hermes/plans/ without editing any project files.

Where are plan files saved in plan mode?▼

Plans are saved under .hermes/plans/ with a timestamped filename like YYYY-MM-DD_HHMMSS-<slug>.md, relative to the active workspace. If the runtime provides a specific target path, that exact path is used instead.

Does plan mode work on remote or docker workspaces?▼

Yes. The plan path is relative to the active working directory, and the file tools are backend-aware, so plans are saved correctly on local, docker, ssh, modal, and daytona backends.

What should a good implementation plan include?▼

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

Can plan mode run terminal commands or commit changes?▼

No. Plan mode prohibits mutating terminal commands, commits, pushes, and external actions. Only read-only inspection commands are allowed, and the single writable output is the plan markdown file itself.

Related Skills

Explore More Software Engineering Skills→
The-InterdependencyThe-Interdependency
1

brainstorming

Translate user requirements into actionable design options with trade-offs.

Official
Advanced
discountedcookiediscountedcookie

openspec-apply

Execute approved OpenSpec change tasks step-by-step with test-tdd verification.

Community
Advanced
openimagingdataopenimagingdata
2

plan-orchestrator

Coordinate multi-phase plan implementation by orchestrating implement-evaluate cycles among subagents.

Official
Advanced
dimsourdimsour
2

quick

Make small code changes and verify them with build and test commands.

Community
Basic